From: Matthias Klose <doko@ubuntu.com>
To: java-patches@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix linking with -findirect-dispatch
Date: Tue, 16 Apr 2013 09:55:00 -0000 [thread overview]
Message-ID: <516D2004.8030701@ubuntu.com> (raw)
In-Reply-To: <20130416094852.GO12880@tucnak.redhat.com>
Am 16.04.2013 11:48, schrieb Jakub Jelinek:
> On Tue, Apr 16, 2013 at 11:37:07AM +0200, Andreas Schwab wrote:
>> Jakub Jelinek <jakub@redhat.com> writes:
>>
>>> at dynamic link time it is a dummy library with no symbols that just
>>> adds DT_NEEDED of the latest and greatest libgcj.so.N, which provides
>>> all the symbols.
>>
>> Which is exactly the problem. --no-copy-dt-needed-entries has been the
>> default for a long time now.
>
> Why would that be a problem? libgcj.so the linker sees (i.e. the dummy
> library) doesn't intentionally have DT_NEEDED libgcj.so.N, programs and
> shared libraries linked with -findirect-dispatch should be adding
> libgcj_bc.so to DT_NEEDED, not libgcj.so.N.
>
> If this is caused by some recent broken linker change, then that should be
> better reverted.
I don't see this with binutils 2.23.2.
next prev parent reply other threads:[~2013-04-16 9:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 8:36 Andreas Schwab
2013-04-16 8:39 ` Jakub Jelinek
2013-04-16 8:59 ` Bryce McKinlay
2013-04-16 9:13 ` Andreas Schwab
2013-04-16 9:19 ` Jakub Jelinek
2013-04-16 9:37 ` Andreas Schwab
2013-04-16 9:49 ` Jakub Jelinek
2013-04-16 9:55 ` Matthias Klose [this message]
2013-04-26 11:22 ` Matthias Klose
2013-04-26 11:50 ` Andrew Haley
2013-04-16 9:57 ` Andreas Schwab
2013-04-16 10:08 ` Jakub Jelinek
2013-04-16 10:11 ` Andreas Schwab
2013-04-16 10:26 ` Jakub Jelinek
2013-04-16 10:31 ` Andreas Schwab
2013-04-16 16:13 ` Andreas Schwab
2013-04-16 16:19 ` Jakub Jelinek
2013-04-16 17:22 ` Andreas Schwab
2013-06-03 10:56 ` Andreas Schwab
2013-04-16 16:39 ` Bryce McKinlay
2013-04-17 13:17 ` Andreas Schwab
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=516D2004.8030701@ubuntu.com \
--to=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@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: link
Be 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).