[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/24709] New: [arm] linker crash and assertion failure with CMSE

From: clyon at gcc dot gnu.org
Subject: [Bug ld/24709] New: [arm] linker crash and assertion failure with CMSE
Date: Thu, 20 Jun 2019 15:04:40 +0000


            Bug ID: 24709
           Summary: [arm] linker crash and assertion failure with CMSE
           Product: binutils
           Version: 2.33 (HEAD)
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: clyon at gcc dot gnu.org
  Target Milestone: ---


When running the GCC testsuite for target arm-none-eabi with
-mthumb/-march=armv8-m.main+dsp/-mcpu=cortex-m33/-mfloat-abi=soft we have
noticed that several tests fails in gcc.target/arm/cmse:
bitfield-[123].c struct-1.c
collect2: fatal error: ld terminated with signal 11 [Segmentation fault], core
compilation terminated.
/arm-none-eabi/bin/ld: BFD (GNU Binutils) assertion fail

These tests are linked with -Wl,--section-start,.gnu.sgstubs=0x20400000, and I
think the problem is the result of a bad interaction between CMSE stubs and
far-call stubs. When using 0x00400000 instead, the tests pass.

I plan to have a look at the issue, but if someone from ARM could confirm which
config they are using to run these GCC tests, it could be helpful. Actually I'm
wondering how/if it can pass at all, but OTOH I think if this address was
hardcoded in the GCC testsuite, it means that the test was passing at some

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]