Re: ia64-elf and i386-elf fail to build

2016-08-25 Thread Nick Clifton
Hi Joseph, >> * config/ia64/ia64.c (ia64_init_builtins): Initialise the >> float128_type_node if that has not been done already. >> * config/i386/i386.c (ix86_init_builtin_types): Likewise. > > No, this is wrong. The global node must remain as NULL when the type is > not fully

Re: ia64-elf and i386-elf fail to build

2016-08-25 Thread Joseph Myers
On Thu, 25 Aug 2016, Nick Clifton wrote: > gcc/ChangeLog > 2016-08-25 Nick Clifton > > * config/ia64/ia64.c (ia64_init_builtins): Initialise the > float128_type_node if that has not been done already. > * config/i386/i386.c (ix86_init_builtin_types):

Re: ia64-elf and i386-elf fail to build

2016-08-25 Thread Nick Clifton
Hi Guys, > I think this indicates that i386 and ia64 need their own local version of > float128_type_node, set up like float80_type_node (i.e. copied from the > global one if that isn't NULL, otherwise set up locally) instead of using > the global one unconditionally, because of the existence

Re: ia64-elf and i386-elf fail to build

2016-08-25 Thread Joseph Myers
On Thu, 25 Aug 2016, Joseph Myers wrote: > _Float128). Though preferable would be to fix all the targets with > IX86_NO_LIBGCC_TFMODE / IX86_MAYBE_NO_LIBGCC_TFMODE / > IA64_NO_LIBGCC_TFMODE so that they include the relevant support code in > libgcc and so no longer need the

Re: ia64-elf and i386-elf fail to build

2016-08-25 Thread Joseph Myers
On Thu, 25 Aug 2016, Nick Clifton wrote: > The cause appears to be an attempt to register a builtin type using > the float128_type_node, which is NULL for these particular targets: > > gcc/config/ia64/ia64.c:10373 > gcc/config/i386/i386.c:33347 > > Presumably float128_type_node

ia64-elf and i386-elf fail to build

2016-08-25 Thread Nick Clifton
Hi Guys, The ia64-elf and i386-elf targets currently fail to build for me using the mainline sources. The symptom is a seg-fault when running the self tests: ./xgcc <...> -xc -S -c /dev/null -fself-test : internal compiler error: Segmentation fault The cause appears to be an