From: "Nathan J. Williams" <nathanw@wasabisystems.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: RFA: general prologue analysis framework
Date: Fri, 07 Oct 2005 21:41:00 -0000 [thread overview]
Message-ID: <mtu64s9roo1.fsf@scrubbing-bubbles.mit.edu> (raw)
In-Reply-To: <20051007213028.GA2371@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> writes:
> If you're guaranteed that the compiler only adjusts the stack pointer
> by constant amounts, either in the prologue or down and then up again
> within a basic block, maybe it would be useful. But very few compilers
> behave that way.
>
> Did your compiler really give you that guarantee?
Observationally, it only ever adjusted the stack pointer by constant
amounts, though it did it wherever it felt like. I don't think the
compiler was smart enough to do anything more complicated than
constant adjustments.
As far as actual guarantees, I have no idea. It was a binary product
and my customer was barely on speaking terms with their compiler
vendor.
- Nathan
next prev parent reply other threads:[~2005-10-07 21:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 20:39 Jim Blandy
2005-10-07 21:25 ` Nathan J. Williams
2005-10-07 21:30 ` Daniel Jacobowitz
2005-10-07 21:41 ` Nathan J. Williams [this message]
2005-10-08 7:02 ` Jim Blandy
2005-10-08 7:01 ` Jim Blandy
2005-10-08 16:00 ` Daniel Jacobowitz
2005-10-09 20:27 ` Daniel Jacobowitz
2005-10-13 0:20 ` Jim Blandy
2005-10-13 1:04 ` Daniel Jacobowitz
2005-10-13 13:50 ` Ulrich Weigand
2005-10-13 17:17 ` Jim Blandy
2005-10-13 17:48 ` Ulrich Weigand
2005-10-13 18:03 ` Daniel Jacobowitz
2005-10-14 18:13 ` Jim Blandy
2005-10-17 18:52 ` Ulrich Weigand
2005-10-17 20:28 ` Jim Blandy
2005-11-23 2:56 ` Ulrich Weigand
2005-10-15 12:12 ` Eli Zaretskii
2005-10-17 20:32 ` Jim Blandy
2005-10-19 8:55 ` Eli Zaretskii
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=mtu64s9roo1.fsf@scrubbing-bubbles.mit.edu \
--to=nathanw@wasabisystems.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@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