[Bug other/54671] New: gcc 4.7.2 -Wl,--no-ctors-in-init-array causes binutils test failure, works with 4.7.1

[Bug other/54671] New: gcc 4.7.2 -Wl,--no-ctors-in-init-array causes binutils test failure, works with 4.7.1

[ncahill_alt at yahoo dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54671

             Bug #: 54671
           Summary: gcc 4.7.2 -Wl,--no-ctors-in-init-array causes binutils
                    test failure, works with 4.7.1
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: other
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ncahill_alt@yahoo.com


Created attachment 28249
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28249
broken output file and generating makefile

binutils-2.22/gold has an extra test failure when built with gcc 4.7.2.  This
is the offending command:

gcc -Bgcctestdir/ -Wl,--no-ctors-in-init-array -Wl,-O1,--as-needed -o
broken_by_gcc_472 a.o

With 4.7.1, the test passes.  I have put this in the 'other' category as no
compilation seems to be taking place.

In the attachment, you'll find output files generated with 4.7.2 and 4.7.1 to
compare, hopefully the second is obviously broken.  Also there is a Makefile to
run the offending command, and preprocessed source for the object file being
used.

Thank you, hope this is enough to find/fix the error.

Neil Cahill.

[Bug other/54671] gcc 4.7.2 -Wl,--no-ctors-in-init-array causes binutils test failure, works with 4.7.1

[ncahill_alt at yahoo dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54671

--- Comment #1 from ncahill_alt at yahoo dot com 2012-09-22 19:00:06 UTC ---
gcc -v:


Using built-in specs.
COLLECT_GCC=/usr/i686-pc-linux-gnu/gcc-bin/4.7.2/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-pc-linux-gnu/4.7.2/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.7.2/configure --disable-bootstrap --disable-libada
--disable-ld --disable-gold --enable-lto --enable-libssp
--enable-cloog-backend=isl --without-cloog --prefix=/usr
--bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.7.2
--includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.7.2/include
--datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.7.2
--mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.7.2/man
--infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.7.2/info
--with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.7.2/include/g++-v4
--host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec
--disable-fixed-point --without-ppl --enable-nls --without-included-gettext
--with-system-zlib --disable-werror --enable-secureplt --disable-multilib
--enable-libmudflap --disable-libgomp
--with-python-dir=/share/gcc-data/i686-pc-linux-gnu/4.7.2/python
--enable-checking=release --disable-libgcj --enable-languages=c,c++,fortran,lto
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --with-bugurl=http://bugs.gentoo.org/
Thread model: posix
gcc version 4.7.2 (GCC) 

Neil.

[Bug other/54671] [4.7/4.8 Regression] gcc 4.7.2 -Wl,--no-ctors-in-init-array causes binutils test failure, works with 4.7.1

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54671

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |i?86-*-*
      Known to work|                            |4.7.1
   Target Milestone|---                         |4.7.3
            Summary|gcc 4.7.2                   |[4.7/4.8 Regression] gcc
                   |-Wl,--no-ctors-in-init-arra |4.7.2
                   |y causes binutils test      |-Wl,--no-ctors-in-init-arra
                   |failure, works with 4.7.1   |y causes binutils test
                   |                            |failure, works with 4.7.1
      Known to fail|                            |4.7.2

[Bug other/54671] [4.7/4.8 Regression] gcc 4.7.2 -Wl,--no-ctors-in-init-array causes binutils test failure, works with 4.7.1

[jakub at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54671

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-09-24 10:13:53 UTC ---
I think this is a user bug.  If gcc is configured against binutils that support
conversion of ctors into init_array, then it will assume it, obviously you
can't use --no-ctors-in-init-array then, you'd need to configure gcc not to
assume it.
Why do you need to use that option (actually, I wonder why the linker has that
option at all)?

[Bug other/54671] [4.7/4.8 Regression] gcc 4.7.2 -Wl,--no-ctors-in-init-array causes binutils test failure, works with 4.7.1

[ncahill_alt at yahoo dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54671

--- Comment #3 from ncahill_alt at yahoo dot com 2012-09-24 20:14:04 UTC ---
>From what I understand, gold's failing test assumes that gcc will make
available in general the old functionality, functionality that certain BSD
derived systems lacking the .init_array ELF section require(d), but which glibc
has not used in 10 years.  What can I say, the test is wrong.

I will report this to binutils, that the initpri3b test should disclaim or run
only when the system-default is a separate .ctors section.

Thank you, Jakub, for the quick response and clarification.

Neil.

[Bug other/54671] [4.7/4.8 Regression] gcc 4.7.2 -Wl,--no-ctors-in-init-array causes binutils test failure, works with 4.7.1

[pluto at agmk dot net]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54671

--- Comment #4 from Pawel Sikora <pluto at agmk dot net> 2012-09-25 19:23:15 UTC ---
(In reply to comment #2)
> I think this is a user bug.  If gcc is configured against binutils that support
> conversion of ctors into init_array, then it will assume it, obviously you
> can't use --no-ctors-in-init-array then, you'd need to configure gcc not to
> assume it.
> Why do you need to use that option (actually, I wonder why the linker has that
> option at all)?

e.g. i'd like to build an application for an old enterprise distro
(which doesn't support init/fini arrays) on my brand new distro.
-Wl,--no-ctors-in-init-array works perfectly fine in this case.

[Bug other/54671] [4.7/4.8 Regression] gcc 4.7.2 -Wl,--no-ctors-in-init-array causes binutils test failure, works with 4.7.1

[jakub at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54671

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-07 18:16:12 UTC ---
You should then configure your compiler with --disable-initfini-array.