On 29/04/15 00:27, Joseph Myers wrote: > On Mon, 20 Apr 2015, Szabolcs Nagy wrote: > >> * On powerpc it seems the only configure option to choose the default >> long-double abi is --with-long-double-128, but that's the default with >> sufficiently new glibc. (musl gets 64bit long-double because the glibc >> version check fails, this is ok, because there is no ibm128 support in >> musl, but it would be better if --with-long-double-64 could be set >> explicitly or even ieee128 abi if gcc supports that). > > It should be possible to use --without-long-double-128 (if not, that's a > bug). >
ok, --without-long-double-128 works, i thought i tested it >> * gcc stdatomic.h has some incompatible typedefs with musl stdint.h > > If musl has chosen stdint.h types different from those in glibc, you need > to make the *_TYPE macros appropriately conditional (possibly making > glibc-stdint.h include conditionals to select the musl types when musl is > in use). > only affects [u]int_fastN_t types (on 64bit systems for N=16,32 musl uses int but glibc uses long) i can fix glibc-stdint.h, but it's yet another way in which the compiler is tied to a particular libc. (using musl-stdint.h would be nicer, but that would require more changes i think, i have a fix now where the glibc-stdint.h types depend on OPTION_MUSL, but i still have to make sure OPTION_MUSL is always defined when this header is used). (i'd prefer if the compiler did not know about these types, but the standard requires them in stdatomic.h without including stdint.h and in stdint.h in freestanding mode, i'm not sure if there is a workaround without depending on libc)
