public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rdsandiford@googlemail.com>
To: gcc-patches@gcc.gnu.org
Subject: PING: [df] Always mark the stack pointer as defined on entry.
Date: Wed, 03 Sep 2008 19:13:00 -0000	[thread overview]
Message-ID: <8763pdcami.fsf@firetop.home> (raw)

http://gcc.gnu.org/ml/gcc-patches/2008-08/msg02236.html
Tell DF that the incoming stack pointer is always important.
The current code assumes that the initial value of the stack
pointer isn't relevant once the prologue has been generated.

Richard

             reply	other threads:[~2008-09-03 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 19:13 Richard Sandiford [this message]
2008-09-03 19:23 ` H.J. Lu
2008-09-03 19:23   ` Richard Sandiford
2008-09-05  7:49     ` Ye, Joey
2008-09-03 22:04 ` 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=8763pdcami.fsf@firetop.home \
    --to=rdsandiford@googlemail.com \
    --cc=gcc-patches@gcc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).