This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/58278] visibility bug from #26905 still happens with the sparc64 backend
- From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 30 Aug 2013 20:52:58 +0000
- Subject: [Bug target/58278] visibility bug from #26905 still happens with the sparc64 backend
- Auto-submitted: auto-generated
- References: <bug-58278-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58278
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Compare with this on amd64:
>
> > c++ -o plain.s -S conftest.cc
> > c++ -o shared.s -fPIC -shared -S conftest.cc
> > diff -u plain.s shared.s
> --- plain.s 2013-08-30 21:46:18.000000000 +0200
> +++ shared.s 2013-08-30 21:46:25.000000000 +0200
> @@ -10,7 +10,7 @@
> movq %rsp, %rbp
> .cfi_offset 6, -16
> .cfi_def_cfa_register 6
> - call _ZN10TestStruct4InitEv
> + call _ZN10TestStruct4InitEv@PLT
> popq %rbp
> .cfi_def_cfa 7, 8
> ret
>
> while on sparc (and sparc64) there is no difference.
So what? What happens if conftest.cc doesn't fiddle with visibility at all?