From: Jim Blandy <jimb@red-bean.com>
To: Jim Blandy <jimb@red-bean.com>,
pgilliam@us.ibm.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] add 'rs6000_in_function_epilogue_p()'
Date: Sun, 04 Dec 2005 21:22:00 -0000 [thread overview]
Message-ID: <8f2776cb0512022143y27cbcfcat3cbcd1c2a49e6286@mail.gmail.com> (raw)
In-Reply-To: <20051203045349.GA24721@nevyn.them.org>
On 12/2/05, Daniel Jacobowitz <drow@false.org> wrote:
> Fascinating. So, do both prologue and epilogue recognition. It would
> be useful for backtraces in epilogues, but not for much else, and it
> would be a lot of work, so I have trouble seeing this get implemented.
> But, maybe.
Well, I was suggesting that Paul do it, you see. :)
(I don't think it'd be that much work.)
> Of course this is only useful without CFI and the main reason PPC
> doesn't use CFI has been solved. And the problem is likely to
> reoccur with CFI that doesn't describe the epilogue, which today is
> prevalent.
As I've always said, compiler-provided CFI is better.
next prev parent reply other threads:[~2005-12-03 5:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 23:56 Paul Gilliam
2005-12-01 5:21 ` Jim Blandy
2005-12-01 18:27 ` Paul Gilliam
2005-12-01 20:14 ` Paul Gilliam
2005-12-02 1:13 ` Jim Blandy
2005-12-02 1:23 ` Daniel Jacobowitz
2005-12-02 20:12 ` Paul Gilliam
2005-12-02 20:17 ` Paul Gilliam
2005-12-03 3:05 ` Jim Blandy
2005-12-02 23:38 ` Jim Blandy
2005-12-04 20:19 ` Daniel Jacobowitz
2005-12-04 18:59 ` Daniel Jacobowitz
2005-12-04 20:48 ` Jim Blandy
2005-12-04 21:12 ` Jim Blandy
2005-12-04 21:16 ` Daniel Jacobowitz
2005-12-04 21:22 ` Jim Blandy [this message]
2005-12-02 4:02 ` Joel Brobecker
2005-12-02 18:44 ` Mark Kettenis
2005-12-02 19:15 ` [PATCH] add 'rs6000_in_function_epilogue_p()' (Revised) Paul Gilliam
2005-12-02 20:28 ` Mark Kettenis
2005-12-02 21:19 ` Daniel Jacobowitz
2005-12-02 21:21 ` Mark Kettenis
2005-12-03 4:53 ` [PATCH] add 'rs6000_in_function_epilogue_p()' (Revised, again) Paul Gilliam
2005-12-03 5:43 ` Paul Gilliam
2005-12-02 21:44 ` [PATCH] add 'rs6000_in_function_epilogue_p()' (Revised) Kevin Buettner
2005-12-06 15:20 ` Paul Gilliam
2005-12-06 15:15 ` Paul Gilliam
2005-12-08 4:42 ` Kevin Buettner
2006-01-11 17:44 ` Paul Gilliam
2006-01-12 0:12 ` Paul Gilliam
2006-01-12 23:53 ` Paul Gilliam
2006-01-13 21:05 ` Mark Kettenis
2006-01-17 3:46 ` Paul Gilliam
2006-01-17 19:29 ` Mark Kettenis
2006-02-09 17:46 ` Kevin Buettner
2005-12-02 22:19 ` Jim Blandy
2005-12-02 22:28 ` Daniel Jacobowitz
2005-12-02 23:20 ` Jim Blandy
2005-12-03 12:48 ` Paul Gilliam
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=8f2776cb0512022143y27cbcfcat3cbcd1c2a49e6286@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb-patches@sourceware.org \
--cc=pgilliam@us.ibm.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