From: Andreas Schwab <aschwab@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: Don't overshoot when executing cfa instructions
Date: Mon, 29 Jun 2009 13:19:00 -0000 [thread overview]
Message-ID: <m3k52vtbxu.fsf@hase.home> (raw)
In-Reply-To: <20090627223341.GB14420@caradoc.them.org> (Daniel Jacobowitz's message of "Sat, 27 Jun 2009 18:33:41 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> Actually, before approving this I have a question. What about state
> changes caused by the branch?
>
> I remember a similar problem with location lists. Before the branch,
> a variable lives at some location. Inside the called function, it is
> gone. Did we ever find a representation for that? Does it rely
> on the instruction after the branch marking the register as clobbered?
Do you have a testcase, or a hint how to create one?
Andreas.
--
Andreas Schwab, aschwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
next prev parent reply other threads:[~2009-06-29 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 22:23 Andreas Schwab
2009-06-27 22:28 ` Daniel Jacobowitz
2009-06-27 22:33 ` Daniel Jacobowitz
2009-06-29 13:19 ` Andreas Schwab [this message]
2009-06-29 14:33 ` Daniel Jacobowitz
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=m3k52vtbxu.fsf@hase.home \
--to=aschwab@redhat.com \
--cc=gdb-patches@sourceware.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