public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aph at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/37068] [4.4 Regression] libgcj linkage failure: Incorrect library ABI version detected Date: Mon, 03 Nov 2008 15:13:00 -0000 [thread overview] Message-ID: <20081103151227.2255.qmail@sourceware.org> (raw) In-Reply-To: <bug-37068-276@http.gcc.gnu.org/bugzilla/> ------- Comment #18 from aph at redhat dot com 2008-11-03 15:12 ------- Subject: Re: [4.4 Regression] libgcj linkage failure: Incorrect library ABI version detected dave at hiauly1 dot hia dot nrc dot ca wrote: > ------- Comment #17 from dave at hiauly1 dot hia dot nrc dot ca 2008-11-03 15:02 ------- > Subject: Re: [4.4 Regression] libgcj linkage failure: Incorrect library ABI > version detected > >> ------- Comment #13 from aph at gcc dot gnu dot org 2008-11-03 10:18 ------- >> As a Java maintainer I'm happy to have a look at this, but I have no access to >> HP/UX hardware. > > I could provide access. However, debugging this with gdb is tricky. > It can't set a breakpoint in a constructor in a shared library. There's > some issue with load notifications. It's also not possible to link > with -static. That doesn't matter, because it's not a runtime bug, it's a compiler bug. We have to debug the compiler. > I'm willing to look at anything you suggest. There's a couple of > other PRs related to gcj-dbtool that probably relate to this problem. > > The org-xml.list is one in which I see the same class registered twice > (e.g., _ZN3org3xml3sax3ext14LexicalHandler6class$E). Okay, the question is why is cgraph_build_static_cdtor() being called twice, once from cgraph_optimize() and once from java_parse_file() ? And, if the FE should not call cgraph_build_static_cdtor(), why does the code generation fail if the call is removed ? The entire solution to this problem lies in that answer. Andrew. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37068
next prev parent reply other threads:[~2008-11-03 15:13 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-09 14:59 [Bug java/37068] New: " danglin at gcc dot gnu dot org 2008-08-10 19:56 ` [Bug java/37068] " pinskia at gcc dot gnu dot org 2008-08-22 15:23 ` rguenth at gcc dot gnu dot org 2008-09-09 12:56 ` hubicka at gcc dot gnu dot org 2008-10-16 20:13 ` dje at gcc dot gnu dot org 2008-10-30 23:30 ` dave at hiauly1 dot hia dot nrc dot ca 2008-10-31 4:24 ` dave at hiauly1 dot hia dot nrc dot ca 2008-10-31 17:20 ` ro at gcc dot gnu dot org 2008-10-31 19:51 ` dave at hiauly1 dot hia dot nrc dot ca 2008-10-31 23:32 ` dave at hiauly1 dot hia dot nrc dot ca 2008-11-01 16:20 ` danglin at gcc dot gnu dot org 2008-11-01 16:51 ` dave at hiauly1 dot hia dot nrc dot ca 2008-11-02 2:34 ` dave at hiauly1 dot hia dot nrc dot ca 2008-11-03 10:19 ` aph at gcc dot gnu dot org 2008-11-03 11:55 ` jakub at gcc dot gnu dot org 2008-11-03 14:29 ` dave at hiauly1 dot hia dot nrc dot ca 2008-11-03 14:47 ` aph at gcc dot gnu dot org 2008-11-03 14:53 ` jakub at gcc dot gnu dot org 2008-11-03 15:03 ` dave at hiauly1 dot hia dot nrc dot ca 2008-11-03 15:13 ` aph at redhat dot com [this message] 2008-11-03 17:37 ` dje at gcc dot gnu dot org 2008-11-03 17:40 ` mmitchel at gcc dot gnu dot org 2008-11-03 17:42 ` jakub at gcc dot gnu dot org 2008-11-03 17:49 ` aph at gcc dot gnu dot org 2008-11-04 5:52 ` mark at codesourcery dot com 2008-11-04 10:33 ` aph at gcc dot gnu dot org 2008-11-04 16:10 ` aph at redhat dot com 2008-11-04 18:12 ` dje dot gcc at gmail dot com 2008-11-04 18:17 ` aph at redhat dot com 2008-11-04 18:17 ` dje dot gcc at gmail dot com 2008-11-04 18:20 ` aph at gcc dot gnu dot org 2008-11-04 18:35 ` dje at gcc dot gnu dot org 2008-11-04 19:02 ` dave at hiauly1 dot hia dot nrc dot ca 2008-11-04 23:08 ` aph at redhat dot com 2008-11-05 1:12 ` dave at hiauly1 dot hia dot nrc dot ca 2008-11-05 10:08 ` aph at gcc dot gnu dot org 2008-11-05 10:16 ` jakub at gcc dot gnu dot org 2008-11-05 13:41 ` ro at techfak dot uni-bielefeld dot de 2008-11-05 14:03 ` aph at redhat dot com 2008-11-05 15:09 ` ro at techfak dot uni-bielefeld dot de 2008-11-05 15:47 ` dje at gcc dot gnu dot org
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=20081103151227.2255.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).