This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/57366] gcc.dg/lto/attr-weakref-1 FAILs
- From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 22 May 2013 14:44:22 +0000
- Subject: [Bug middle-end/57366] gcc.dg/lto/attr-weakref-1 FAILs
- Auto-submitted: auto-generated
- References: <bug-57366-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57366
--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
> Thank you. It seems that the weakref is simply not output into the file, so we
> end up with undefined call.
Which may or may not be the same problem as in PR lto/47333.
> What happens when you compile the following manually concatenated testcase w/o
> LTO? If it links, can you attach the assembly? I am bit unsure how non-weakref
> targets are supposed to behave in situations like this.
It links without problems.
> I convinced myself that for LTO one needs GNU binutils and thus weakref is
> supported, but it is obviously not always the case ;)
All other LTO testcases have long worked with Solaris as and ld
(i.e. without weakref and linker plugin), and until the 4.7 branch with
gas and IRIX ld.
Rainer