From: "H.J. Lu" <hjl@lucon.org>
To: Ian Lance Taylor <iant@google.com>,
binutils@sourceware.org, rth@redhat.com,
richard@codesourcery.com
Subject: Re: Fix assertion failure on aliases of dynamic weak symbols
Date: Wed, 18 Jul 2007 21:06:00 -0000 [thread overview]
Message-ID: <20070718191022.GA24694@lucon.org> (raw)
In-Reply-To: <87644hzost.fsf@firetop.home>
On Wed, Jul 18, 2007 at 04:58:42PM +0100, Richard Sandiford wrote:
> "H.J. Lu" <hjl@lucon.org> writes:
> > I think the proper way to fix this is
> >
> > 1. Select a different section for linker created symbol to avoid false
> > symbol alias in a shared library.
>
> I disagree. If the linker script defines a symbol in a section statement,
> why shouldn't the symbol belong to that section? I'm bet folk out there
> are relying on that behaviour.
>
I had an impression that linker tried to pick a section for linker
defined symbols. I was wrong.
H.J.
next prev parent reply other threads:[~2007-07-18 19:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 17:13 Richard Sandiford
2007-07-16 21:33 ` H.J. Lu
2007-07-17 1:12 ` PATCH: Remove u.weakdef from elf_link_hash_entry H.J. Lu
2007-07-17 5:39 ` Fix assertion failure on aliases of dynamic weak symbols Ian Lance Taylor
2007-07-17 13:55 ` H.J. Lu
2007-07-17 19:31 ` Ian Lance Taylor
2007-07-18 15:58 ` H.J. Lu
2007-07-18 18:23 ` Richard Sandiford
2007-07-18 21:06 ` H.J. Lu [this message]
2007-07-19 19:56 ` PATCH: Check symbol type for symbol alias H.J. Lu
2007-07-20 12:50 ` Richard Sandiford
2007-07-20 13:07 ` H.J. Lu
2007-07-20 15:03 ` Richard Sandiford
2007-07-20 17:05 ` H.J. Lu
2007-07-21 8:55 ` Richard Sandiford
2007-07-23 5:35 ` H.J. Lu
2007-07-23 10:05 ` Fix assertion failure on aliases of dynamic weak symbols Alan Modra
2007-07-23 11:43 ` Richard Sandiford
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=20070718191022.GA24694@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sourceware.org \
--cc=iant@google.com \
--cc=richard@codesourcery.com \
--cc=rth@redhat.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).