From: David Mosberger <davidm@napali.hpl.hp.com>
To: James E Wilson <wilson@specifixinc.com>
Cc: "H. J. Lu" <hjl@lucon.org>, David Mosberger <davidm@hpl.hp.com>,
binutils@sources.redhat.com
Subject: Re: PATCH: Don't allow ia64 unwind section to point to section in different files
Date: Tue, 17 May 2005 21:28:00 -0000 [thread overview]
Message-ID: <17034.22889.764624.616301@napali.hpl.hp.com> (raw)
In-Reply-To: <1116362267.7961.46.camel@aretha.corp.specifixinc.com>
>>>>> On Tue, 17 May 2005 13:38:57 -0700, James E Wilson <wilson@specifixinc.com> said:
Jim> On Fri, 2005-05-13 at 14:46, H. J. Lu wrote:
>> When weak functions are used on ia64, part of the unwind section may
>> point to the strong definition in a different file. This will lead to
>> wrong unwind info. Basically, on ia64, we have to use comdat to get the
>> right unwind info. This patch will check it.
Jim> This doesn't look like the right fix to me.
Jim> I looked at the unwind info with old and new binutils, and noticed that
Jim> the relocs are different. In old binutils, we have
Jim> RELOCATION RECORDS FOR [.IA_64.unwind]:
Jim> OFFSET TYPE VALUE
Jim> 0000000000000000 SEGREL64LSB .text
Jim> in new binutils we have
Jim> RELOCATION RECORDS FOR [.IA_64.unwind]:
Jim> OFFSET TYPE VALUE
Jim> 0000000000000000 SEGREL64LSB _start
Jim> Since _start is at offset 0 in .text, these are the same value normally,
Jim> but they aren't if we have duplicate weak/strong functions. Since the
Jim> unwind info should always bind locally, I think it is wrong to have the
Jim> unresolved _start symbol here.
Ah, so it wasn't by coincidence that the old(er) binutils worked right.
It's encouraging to see that this problem is eminently fixable.
--david
next prev parent reply other threads:[~2005-05-17 20:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CBDB88BFD06F7F408399DBCF8776B3DC0424E404@scsmsx403.amr.corp.intel.com>
[not found] ` <17029.3906.33841.302589@napali.hpl.hp.com>
[not found] ` <20050513205004.GB30928@lucon.org>
[not found] ` <17029.5402.827349.738563@napali.hpl.hp.com>
[not found] ` <20050513210111.GB31069@lucon.org>
[not found] ` <17029.5812.552722.635968@napali.hpl.hp.com>
2005-05-13 21:58 ` H. J. Lu
2005-05-14 0:28 ` H. J. Lu
2005-05-16 13:58 ` David Mosberger
2005-05-16 14:29 ` H. J. Lu
2005-05-17 20:52 ` James E Wilson
2005-05-17 21:28 ` David Mosberger [this message]
2005-05-17 22:56 ` H. J. Lu
2005-05-18 0:15 ` James E Wilson
2005-05-18 0:15 ` H. J. Lu
2005-05-18 7:02 Jan Beulich
2005-05-18 13:58 ` H. J. Lu
2005-05-18 7:23 Jan Beulich
[not found] <s28af68c.020@emea1-mh.id2.novell.com>
2005-05-18 8:06 ` David Mosberger
2005-05-18 15:16 Jan Beulich
2005-05-18 15:21 ` H. J. Lu
2005-05-18 15:26 ` David Mosberger
2005-05-18 15:33 ` H. J. Lu
2005-05-18 16:27 ` David Mosberger
2005-05-18 19:35 ` James E Wilson
2005-05-19 8:26 Jan Beulich
2005-05-19 15:18 ` Daniel Jacobowitz
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=17034.22889.764624.616301@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=binutils@sources.redhat.com \
--cc=davidm@hpl.hp.com \
--cc=hjl@lucon.org \
--cc=wilson@specifixinc.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).