http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60594
--- Comment #3 from Chandler Carruth ---
Personally, I've no idea what the standard says.
However, it seems extremely useful to be able to freely use std::function with
return types (and argument types) within the definition those types which is
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60490
--- Comment #5 from Chandler Carruth ---
(In reply to Eric Christopher from comment #4)
> I disagree for bare metal that including endian is the right way, but agree
> that __BYTE_ORDER__ is the right way to do this in general.
>
> Thanks Jakub.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60490
--- Comment #7 from Chandler Carruth ---
(In reply to Jakub Jelinek from comment #6)
> Just look what GCC does?
> Say on x86_64 it does:
> gcc -E -dD -xc /dev/null | grep ENDIAN
> #define __ORDER_LITTLE_ENDIAN__ 1234
> #define __ORDER_BIG_ENDIAN__
