From: Richard Henderson <rth@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Michal Ludvig <mludvig@suse.cz>,
Daniel Jacobowitz <drow@mvista.com>, gdb <gdb@sources.redhat.com>
Subject: Re: [testsuite & dwarf2] How to handle store.exp failure on AMD64?
Date: Wed, 13 Aug 2003 04:54:00 -0000 [thread overview]
Message-ID: <20030813045405.GB11912@redhat.com> (raw)
In-Reply-To: <3F39B678.70409@redhat.com>
On Tue, Aug 12, 2003 at 11:54:32PM -0400, Andrew Cagney wrote:
> I would have expected the CIE.INITIAL_INSTRUCTIONS to specify the
> default state of all DWARF2 registers, and not just a select few.
Folks already complain unwind info is too large.
As I said, GCC's unwinder assumes DW_CFA_same_value unless otherwise
stated. Since scratch registers aren't live across the call, it
doesn't matter that we don't mark registers DW_CFA_undefined; any
(accurate) debug information you'll find at the call site in the
caller simply won't say that values are live in those registers.
Anything else would be a bug.
So assuming DW_CFA_same_value produces the most compact representation.
r~
next prev parent reply other threads:[~2003-08-13 4:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 8:49 Michal Ludvig
2003-08-07 13:50 ` Daniel Jacobowitz
2003-08-07 14:58 ` Andrew Cagney
2003-08-07 15:02 ` Daniel Jacobowitz
2003-08-07 15:53 ` Andrew Cagney
2003-08-07 21:40 ` Michal Ludvig
2003-08-13 3:54 ` Andrew Cagney
2003-08-13 4:54 ` Richard Henderson [this message]
2003-08-13 14:39 ` Andrew Cagney
2003-08-13 16:50 ` Richard Henderson
2003-08-13 18:23 ` Andrew Cagney
2003-08-13 23:35 ` 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=20030813045405.GB11912@redhat.com \
--to=rth@redhat.com \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mludvig@suse.cz \
/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