From: Mark Kettenis <kettenis@chello.nl>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] dwarf2-frame.c: Support DW_EH_PE_textrel encoding
Date: Thu, 02 Oct 2003 22:10:00 -0000 [thread overview]
Message-ID: <200310022210.h92MAYWe000796@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20031002200652.GX11435@cygbert.vinschen.de> (message from Corinna Vinschen on Thu, 2 Oct 2003 22:06:52 +0200)
Date: Thu, 2 Oct 2003 22:06:52 +0200
From: Corinna Vinschen <vinschen@redhat.com>
Hi,
I'm not sure if the patch is actually 100% correct but I think it's
not far from that.
It looks sensible to me.
For a few weeks now, gcc emits the DW_EH_PE_textrel encoding for sh
and (AFAICS) ia64. This encoding type is unsupported in gdb so far.
The below patch tries to accomodate this encoding.
Is the patch ok as it is? On sh, the testcases failing with a gcc
emitting this encoding run through with the below patch and the
overall FAIL count is the same as before.
I've got a problem with re-using the variable named `got' in
dwarf2_build_frame_info() for the ".text" section. Could you please
rename the variable to something more generic (for example `sect') or
introduce a new variable?
I'd also appreciate it if you changed gcc into GCC in the comment
(thats the spelling the GCC project uses, and makes the sentence start
with a capital). You'll need to add an extra space after the . too.
With those changes, this is OK.
* dwarf2-frame.c (struct comp_unit): Add tbase member to store
base for DW_EH_PE_textrel encodings.
(read_encoded_value): Add a DW_EH_PE_textrel case.
(dwarf2_build_frame_info): Set unit.tbase to beginning of text
section.
next prev parent reply other threads:[~2003-10-02 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 20:07 Corinna Vinschen
2003-10-02 22:10 ` Mark Kettenis [this message]
2003-10-03 8:09 ` Corinna Vinschen
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=200310022210.h92MAYWe000796@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.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