From: Sterling Augustine <sterling@tensilica.com>
To: Andreas Schwab <schwab@suse.de>
Cc: binutils@sourceware.org
Subject: Re: Generate DW_AT_ranges for non-contiguous code
Date: Tue, 10 Oct 2006 20:58:00 -0000 [thread overview]
Message-ID: <452BCF7F.30203@tensilica.com> (raw)
In-Reply-To: <je8xjoxvao.fsf@sykes.suse.de>
[-- Attachment #1: Type: text/plain, Size: 124 bytes --]
Andreas Schwab wrote:
> [...] That ain't gonna work.
Thanks for the catch. Enclosed is a patch which should fix.
Sterling
[-- Attachment #2: ranges_patch --]
[-- Type: text/plain, Size: 796 bytes --]
Index: dwarf2dbg.c
===================================================================
RCS file: /cvs/src/src/gas/dwarf2dbg.c,v
retrieving revision 1.87
diff -d -u -r1.87 dwarf2dbg.c
--- dwarf2dbg.c 8 Aug 2006 19:09:33 -0000 1.87
+++ dwarf2dbg.c 10 Oct 2006 16:48:30 -0000
@@ -1591,13 +1591,10 @@
}
else
{
- /* This attributes is emitted if the code is disjoint. */
+ /* This attribute is emitted if the code is disjoint. */
/* DW_AT_ranges */
- expr.X_op = O_symbol;
- expr.X_add_symbol = section_symbol (ranges_seg);
- expr.X_add_number = 0;
- emit_expr (&expr, sizeof_address);
+ TC_DWARF2_EMIT_OFFSET (section_symbol (ranges_seg), sizeof_offset);
}
/* DW_AT_name. We don't have the actual file name that was present
next prev parent reply other threads:[~2006-10-10 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 23:22 Sterling Augustine
2006-08-07 10:55 ` Nick Clifton
2006-08-07 13:30 ` Daniel Jacobowitz
2006-08-07 14:08 ` Nick Clifton
2006-08-07 14:08 ` Nick Clifton
2006-08-07 20:30 ` Sterling Augustine
2006-08-07 21:46 ` Daniel Jacobowitz
2006-08-07 22:00 ` Sterling Augustine
2006-08-08 8:29 ` Nick Clifton
2006-10-10 11:30 ` Andreas Schwab
2006-10-10 20:58 ` Sterling Augustine [this message]
2006-10-14 9:43 ` Nick Clifton
-- strict thread matches above, loose matches on Subject: below --
2006-07-28 22:06 Sterling Augustine
2006-07-28 21:12 Sterling Augustine
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=452BCF7F.30203@tensilica.com \
--to=sterling@tensilica.com \
--cc=binutils@sourceware.org \
--cc=schwab@suse.de \
/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).