bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/19579] [Regression] link error linking fortran code on s390x-lin


From: krebbel at linux dot vnet.ibm.com
Subject: [Bug ld/19579] [Regression] link error linking fortran code on s390x-linux-gnu
Date: Wed, 02 Mar 2016 03:54:27 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=19579

--- Comment #7 from Andreas Krebbel <krebbel at linux dot vnet.ibm.com> ---
(In reply to H.J. Lu from comment #6)
> I can reproduce it on Fedora 23.  It is a bug in redhat-rpm-config, which
> has redhat-hardened-cc1 and redhat-hardened-ld.  But there is no
> redhat-hardened-f951.  mopac7app.o isn't compiled with PIE/PIC.

In my tests mopac7app.o was built with -fPIC. The problem seems to occur since
this commit:

commit b31bcacc489d6ede2e9bdfa9905de0ebfd919454
Author: H.J. Lu <address@hidden>
Date:   Fri Oct 16 03:14:40 2015 -0700

    Convert mov to lea for loading address of local common symbol

    There is no need to check def_regular when converting mov to lea for
    loading address of local symbols since def_regular may be false for
    common symbols and SYMBOL_REFERENCES_LOCAL is sufficient.

    bfd/

        * elf32-i386.c (elf_i386_convert_mov_to_lea): Don't check
        def_regular.
        * elf64-x86-64.c (elf_x86_64_convert_mov_to_lea): Likewise.


Before that change there was the same problem is currently on S/390:

/bin/sh ../libtool --tag=F77   --mode=link gfortran  -g -O2 -std=legacy
-fno-automatic -fPIC -lm -Wl,--as-needed -Wl,-z,defs -pie -o mopac7 mopac7app.o
libmopac7.la -lm 
gfortran -g -O2 -std=legacy -fno-automatic -fPIC -Wl,--as-needed -Wl,-z
-Wl,defs -pie -o .libs/mopac7 mopac7app.o  ./.libs/libmopac7.so -lm 
-Wl,--rpath -Wl,/home/andreas/mopac/install/lib
/home/andreas/binutils/binutils-before-install/bin/ld: final link failed:
Nonrepresentable section on output
collect2: error: ld returned 1 exit status
make[1]: *** [mopac7] Error 1

-- 
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]