From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/6.0] Better handle unspecified CFI values
Date: Tue, 09 Sep 2003 17:24:00 -0000 [thread overview]
Message-ID: <vt2wuchvptc.fsf@zenia.home> (raw)
In-Reply-To: <20030909033053.GA8904@nevyn.them.org>
Daniel Jacobowitz <drow@mvista.com> writes:
> Yes - normally. On S/390, stdcall, et cetera (anywhere where the hack
> would be wrong) it gets even worse. We can only compute expressions
> describing a memory location where the register is saved, not computed
> values. For stack pointers (and maybe frame pointers on some
> architectures?) this isn't good enough.
Not to pursue unimportant tangents, but why would the hack be wrong on
the S/390? Its frames are normally FP-free, but aside from that,
what's unusual about it?
next prev parent reply other threads:[~2003-09-09 17:24 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 [this message]
2003-09-09 17:35 ` Daniel Jacobowitz
2003-09-10 19:48 ` Richard Henderson
2003-09-10 19:53 ` Daniel Jacobowitz
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=vt2wuchvptc.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=drow@mvista.com \
--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