From: John Marino <dragonflybsd@marino.st>
To: Ian Lance Taylor <iant@google.com>
Cc: binutils@sourceware.org
Subject: Re: gold linker 2.22 regressed for DragonFly [revised testsuite results]
Date: Sun, 22 Jan 2012 20:46:00 -0000 [thread overview]
Message-ID: <4F1C7589.1040907@marino.st> (raw)
In-Reply-To: <mcr7h0j4j76.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
On 1/22/2012 8:43 PM, Ian Lance Taylor wrote:
>
> Sounds like it. There may be a target independent problem here. What
> should the linker do if the version script specifies that a symbol is
> local but the symbol is also defined in a shared library? I think it
> has to make the symbol local despite the definitions, but it sounds like
> that is not happening.
Are you planning to independently verify and modify the linker behavior
if confirmed? From my point of view, there's nothing more to be done
now that the situation is understood.
John
next prev parent reply other threads:[~2012-01-22 20:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 22:16 gold linker 2.22 regressed for DragonFly John Marino
2011-12-02 4:59 ` Ian Lance Taylor
2011-12-02 8:44 ` John Marino
2011-12-02 14:28 ` Ian Lance Taylor
2011-12-31 16:40 ` John Marino
2012-01-02 2:05 ` Ian Lance Taylor
2012-01-02 9:36 ` John Marino
2012-01-02 18:38 ` Ian Lance Taylor
2012-01-02 19:27 ` John Marino
2012-01-02 19:48 ` John Marino
2012-01-02 22:56 ` John Marino
2012-01-03 9:20 ` gold linker 2.22 regressed for DragonFly [revised testsuite results] John Marino
2012-01-05 18:32 ` Ian Lance Taylor
2012-01-06 10:24 ` John Marino
2012-01-06 14:43 ` Ian Lance Taylor
2012-01-06 20:04 ` John Marino
2012-01-22 18:59 ` John Marino
2012-01-22 19:43 ` Ian Lance Taylor
2012-01-22 20:46 ` John Marino [this message]
2012-01-23 16:49 ` Ian Lance Taylor
2012-01-03 19:43 ` gold linker 2.22 regressed for DragonFly Ian Lance Taylor
2012-01-05 17:30 ` John Marino
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=4F1C7589.1040907@marino.st \
--to=dragonflybsd@marino.st \
--cc=binutils@sourceware.org \
--cc=iant@google.com \
/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).