https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116007
--- Comment #6 from Thomas Petazzoni <thomas.petazz...@free-electrons.com> --- Thanks for all the feedback! However, I'm still a bit confused. In one comment you say: > From thbis, it seems powerpc musl likely doesn't have neither double double > nor IEEE quad support and so in that case you can't use --enable-libquadmath > --enable-libquadmath-support. But then in the followup comment you point to https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=8d7be8d614ba028074597c3ab1ee12d9495fde09 which seems to be a fix for the PowerPC/musl case. What should I understand? Also, if something is not supported, shouldn't it bail out during the configure stage, rather than later on at build time? I'm realizing that we have this snippet of code in Buildroot: # PowerPC64 big endian by default uses the elfv1 ABI, and PowerPC 64 # little endian by default uses the elfv2 ABI. However, musl has # decided to use the elfv2 ABI for both, so we force the elfv2 ABI for # Power64 big endian when the selected C library is musl. ifeq ($(BR2_TOOLCHAIN_USES_MUSL)$(BR2_powerpc64),yy) HOST_GCC_COMMON_CONF_OPTS += \ --with-abi=elfv2 \ --without-long-double-128 endif in Buildroot, but that only applies to PowerPC 64 Big Endian. Our comment says that elfv2 ABI is already the default for PowerPC 64 Little Endian, but perhaps we also need something for PowerPC 64 Little Endian anyway ?
