[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

2012-11-07 Thread jakub at gcc dot gnu.org 


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



Jakub Jelinek  changed:



   What|Removed |Added



 Status|UNCONFIRMED |RESOLVED

 Resolution||INVALID



--- Comment #5 from Jakub Jelinek  2012-11-07 
18:16:12 UTC ---

You should then configure your compiler with --disable-initfini-array.

[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

2012-09-25 Thread pluto at agmk dot net 


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



--- Comment #4 from Pawel Sikora  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

2012-09-24 Thread 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

2012-09-24 Thread jakub at gcc dot gnu.org 


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



Jakub Jelinek  changed:



   What|Removed |Added



 CC||jakub at gcc dot gnu.org



--- Comment #2 from Jakub Jelinek  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

2012-09-24 Thread rguenth at gcc dot gnu.org 


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



Richard Guenther  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