[arm] Too strict linker assert?

Hi, While building a newlib-based arm-eabi toolchain with --with-multilib-list=rmprofile, I faced a linker assertion failure in elf32_arm_merge_eabi_attributes (bfd/elf32-arm.c): BFD_ASSERT (in_attr[Tag_ABI_HardFP_use].i == 0) I traced this down to newlib's impure.o containing only data, and thus

Re: GSoC Project Ideas

On 4/1/19 6:40 PM, Patrick Palka wrote: > On Sun, Mar 3, 2019 at 5:16 PM Jeff Law wrote: >> >> On 3/3/19 4:06 PM, Patrick Palka wrote: >>> Hi everyone, >>> >>> I am very interested in working on GCC as part of GSoC this year. A few >>> years >>> ago I was a somewhat active code contributor[1] an

Re: non-volatile automatic variables in setjmp tests

On Mon, 8 Apr 2019 14:00:39 +0100 Jozef Lawrynowicz wrote: > I'll file a bugzilla once I have more concrete details. > > Jozef I filed BZ90032 for what I believe to be a bug during the reload pass. Jozef

Re: [arm] Too strict linker assert?

On 09/04/2019 13:26, Christophe Lyon wrote: > Hi, > > While building a newlib-based arm-eabi toolchain with > --with-multilib-list=rmprofile, I faced a linker assertion failure in > elf32_arm_merge_eabi_attributes (bfd/elf32-arm.c): > BFD_ASSERT (in_attr[Tag_ABI_HardFP_use].i == 0) > > I traced t