From: Daniel Jacobowitz <drow@mvista.com>
To: Richard Henderson <rth@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/6.0] Better handle unspecified CFI values
Date: Wed, 10 Sep 2003 19:53:00 -0000 [thread overview]
Message-ID: <20030910195306.GA10566@nevyn.them.org> (raw)
In-Reply-To: <20030910194754.GC15867@redhat.com>
On Wed, Sep 10, 2003 at 12:47:54PM -0700, Richard Henderson wrote:
> On Mon, Sep 08, 2003 at 11:30:53PM -0400, Daniel Jacobowitz wrote:
> > We can only compute expressions
> > describing a memory location where the register is saved, not computed
> > values.
>
> False. See DW_CFA_expression.
True. See DW_CFA_expression.
20. DW_CFA_expression
The DW_CFA_expression instruction takes two operands: an unsigned
LEB128 value representing a register number, and a DW_FORM_block
value representing a DWARF expression. The required action is to
establish the DWARF expression as the means by which the address in
which the given register contents are found may be computed. The
value of the CFA is pushed on the DWARF evaluation stack prior to
execution of the DWARF expression.
The DW_OP_call2, DW_OP_call4, DW_OP_call_ref and
DW_OP_push_object_address DWARF operators (see Section 2.4.1)
cannot be used in such a DWARF expression.
It computes "the address in which the given register contents are
found". That's not ambiguous, and that's precisely how GCC uses it:
_Unwind_SetGRPtr (context, i, (void *) val);
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-09-10 19:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 0:57 Andrew Cagney
2003-09-06 21:34 ` Daniel Jacobowitz
2003-09-09 3:00 ` Andrew Cagney
2003-09-09 3:30 ` Daniel Jacobowitz
2003-09-09 17:24 ` Jim Blandy
2003-09-09 17:35 ` Daniel Jacobowitz
2003-09-10 19:48 ` Richard Henderson
2003-09-10 19:53 ` Daniel Jacobowitz [this message]
2003-09-10 21:03 ` Richard Henderson
2003-09-07 20:13 ` Mark Kettenis
2003-09-09 3:00 ` Andrew Cagney
2003-09-07 21:17 ` Richard Henderson
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=20030910195306.GA10566@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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