bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/9934] New: arm gnueabi linker often fails with FPE error while l


From: vapier at gentoo dot org
Subject: [Bug ld/9934] New: arm gnueabi linker often fails with FPE error while linking shared libs
Date: 8 Mar 2009 23:47:18 -0000

while building gcc's shared libs, we end up with this error:
collect2: ld terminated with signal 8 [Floating point exception]

i'm attaching a tarball of the objects from glibc/gcc which are used to trigger
this bug.  to reproduce, hopefully you should be able to extract and just run
`./doit.sh` (might have to change the linker invoked).

Raúl Porcel traced this back to a change between 2.18.50.0.4 and 2.18.50.0.5. 
specifically, this commit seems to be the problem:

    2008-02-20  Paul Brook  <address@hidden>
    
        ld/
        * emultempl/armelf.em (OPTION_FIX_V4BX_INTERWORKING): Define.
        (PARSE_AND_LIST_LONGOPTS): Add fix-v4bx-interworking.
        (PARSE_AND_LIST_OPTIONS): Ditto.
        (PARSE_AND_LIST_ARGS_CASES): Handle OPTION_FIX_V4BX_INTERWORKING.
        * emulparams/armelf.sh (OTHER_TEXT_SECTIONS): Add .v4_bx.
        * emulparams/armelf_linux.sh (OTHER_TEXT_SECTIONS): Ditto.
        * emulparams/armnto.sh (OTHER_TEXT_SECTIONS): Ditto.
        * ld.texinfo: Document --fix-v4bx-interworking.

-- 
           Summary: arm gnueabi linker often fails with FPE error while
                    linking shared libs
           Product: binutils
           Version: 2.19
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ld
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: vapier at gentoo dot org
                CC: bug-binutils at gnu dot org,paul at codesourcery dot
                    com,toolchain at gentoo dot org
  GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: arm-softfloat-linux-gnueabi


http://sourceware.org/bugzilla/show_bug.cgi?id=9934

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

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