From: Jim Wilson <wilson@specifix.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sources.redhat.com
Subject: Re: PATCH: PR ld/3191: Linker failed to handle DW_FORM_ref_addr properly
Date: Wed, 20 Sep 2006 19:15:00 -0000 [thread overview]
Message-ID: <1158778090.2519.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20060920052010.GA22345@lucon.org>
On Tue, 2006-09-19 at 22:20 -0700, H. J. Lu wrote:
> We should only do it for DWARF3. But gcc generates DWARF3 info in
> a DWARF2 file.
In DWARF2, the offset size is always 4, so there is no conflict here.
This code will work fine for both DWARF2 and DWARF3.
I do see a problem though, which is that I don't understand where the
64-bit DWARF3 is coming from. Gcc does not emit 64-bit DWARF for any
target except Irix5/6, and the bug report does not say anything about
using a custom modified gcc. I looked at the client.o object file in
the bug report, and there is no 64-bit DWARF there. (The pointers are
64-bit, but the debug info offsets are not.) I don't understand how
this patch can help. There is something that hasn't been explained here
yet.
--
Jim Wilson, GNU Tools Support, http://www.specifix.com
next prev parent reply other threads:[~2006-09-20 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 6:16 H. J. Lu
2006-09-20 11:40 ` H. J. Lu
2006-09-20 14:48 ` Daniel Jacobowitz
2006-09-20 19:15 ` Jim Wilson [this message]
2006-09-20 22:32 ` H. J. Lu
2006-09-21 2:10 ` H. J. Lu
2006-09-21 16:23 ` H. J. Lu
2006-09-28 7:45 ` Jim Wilson
2006-09-28 9:08 ` H. J. Lu
2006-09-20 19:59 ` Jim Wilson
2006-09-20 20:02 ` H. J. Lu
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=1158778090.2519.6.camel@localhost.localdomain \
--to=wilson@specifix.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.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).