From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Mark Kettenis <kettenis@gnu.org>, gdb@sources.redhat.com
Subject: Re: [RFC] Is skip_prologue_using_sal actually usable?
Date: Tue, 09 Nov 2004 16:55:00 -0000 [thread overview]
Message-ID: <20041109160705.GA21477@nevyn.them.org> (raw)
In-Reply-To: <4190D933.5070006@gnu.org>
On Tue, Nov 09, 2004 at 09:50:27AM -0500, Andrew Cagney wrote:
> Mark,
>
> DWARF 2 provides us with the exact location[s] of a prologue end, can we
> use that?
No compiler I know of emits it. GCC could be fixed to. But then which
meaning to you want GCC to give to it? Too much, or too little?
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-11-09 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 14:28 Mark Kettenis
2004-11-09 2:43 ` Randolph Chung
2004-11-09 10:16 ` Daniel Jacobowitz
2004-11-09 14:35 ` Mark Kettenis
2004-11-09 14:51 ` Daniel Jacobowitz
2004-11-09 14:56 ` Andrew Cagney
2004-11-09 16:07 ` Mark Kettenis
2004-11-09 16:55 ` Daniel Jacobowitz [this message]
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=20041109160705.GA21477@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@gnu.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