public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/56353] New: libgcj should be listed on command line for libjava.jni/invocation/PR16923.c Date: Fri, 15 Feb 2013 23:47:00 -0000 [thread overview] Message-ID: <bug-56353-8172@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56353 Bug #: 56353 Summary: libgcj should be listed on command line for libjava.jni/invocation/PR16923.c Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcj AssignedTo: unassigned@gcc.gnu.org ReportedBy: hjl.tools@gmail.com libjava.jni/invocation/PR16923.c behaves differently, depending on linking with gold or ld. _Jv_RegisterClasses is weak reference and libgcj.so isn't on the linker command line. Since libgcj.so isn't on the linker command line, gold resolves _Jv_RegisterClasses to 0 and ld silently resolves it to _Jv_RegisterClasses in libgcj.so: [hjl@gnu-13 testsuite]$ readelf -sWr /tmp/PR16923.gold | grep _Jv_RegisterClasses 8: 0000000000000000 0 NOTYPE WEAK DEFAULT UND _Jv_RegisterClasses 37: 0000000000000000 0 NOTYPE WEAK DEFAULT UND _Jv_RegisterClasses [hjl@gnu-13 testsuite]$ readelf -sWr /tmp/PR16923.bfd | grep _Jv_RegisterClasses 0000000000600cd0 0000000900000007 R_X86_64_JUMP_SLOT 00000000004005e0 _Jv_RegisterClasses + 0 9: 00000000004005e0 0 FUNC WEAK DEFAULT UND _Jv_RegisterClasses 59: 00000000004005e0 0 FUNC WEAK DEFAULT UND _Jv_RegisterClasses [hjl@gnu-13 testsuite]$
next reply other threads:[~2013-02-15 23:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-15 23:47 hjl.tools at gmail dot com [this message] 2013-02-15 23:52 ` [Bug libgcj/56353] " pinskia at gcc dot gnu.org 2013-02-15 23:59 ` hjl.tools at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-56353-8172@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).