Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c++
Subject: Re: On endianness, many #ifdefs, and the need thereof
Date: Wed, 02 Oct 2019 12:54:21 -0700
Organization: None to speak of
Lines: 18
Message-ID: <ln8sq22aaa.fsf@kst-u.example.com>
References: <f48b89a2-f66c-4a73-b8ca-c13e8fe90dd1@googlegroups.com> <qn26kg$1spc$1@adenine.netfront.net> <qn27ad$iro$1@dont-email.me> <F_1lF.91481$zU2.55548@fx01.iad>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="bddf772ed55a11e50268662a0524f54c"; logging-data="7946"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+jmywjOisL4z8jybrs6vlr"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:qdAG/yYUkqJb3Vna21oFl0o134w= sha1:nmSJvdhwdvMGhVk21Ey1tSSYyB8=
Xref: csiph.com comp.lang.c++:68925

scott@slp53.sl.home (Scott Lurndal) writes:
> David Brown <david.brown@hesbynett.no> writes:
[...]
>>The /compiler/ can handle it at compile time - it can figure out the
>>result of this function at compile time and use that in optimisation.
>
> Can it?  How does that work when you're cross-compiling to a different
> architecture (like a microcontroller, for example)?

Presumably the compiler knows the endianness of the target architecture
it's generating code for.  There might be an issue with the compiler not
having that information soon enough, but it could certainly get the
information if it's worthwhile.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */