From: Richard Henderson <rth@redhat.com>
To: Stephen Clarke <Stephen.Clarke@st.com>
Cc: gcc@gcc.gnu.org, geoffk@geoffk.org
Subject: Re: Using and clobbering hard regs in parallel
Date: Fri, 20 Jul 2001 15:27:00 -0000 [thread overview]
Message-ID: <20010720152737.B3659@redhat.com> (raw)
In-Reply-To: <3B5799C5.29E80E47@st.com>
On Thu, Jul 19, 2001 at 07:39:01PM -0700, Stephen Clarke wrote:
> 2. combine.c should preserve the REG_DEAD (reg:SI 4 r4) note on insn 20.
> Rationale: ummm, not sure -- maybe because if flow.c thinks
> the REG_DEAD note should be there, then combine.c should think so too.
This one is correct.
r~
prev parent reply other threads:[~2001-07-20 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 18:32 Stephen Clarke
2001-07-19 18:39 ` Geoff Keating
2001-07-19 19:39 ` Stephen Clarke
2001-07-20 11:38 ` Joern Rennecke
2001-07-20 13:11 ` Mark Mitchell
2001-07-20 13:56 ` Joern Rennecke
2001-07-20 14:02 ` Mark Mitchell
2001-07-20 15:25 ` Richard Henderson
2001-07-20 15:54 ` Joern Rennecke
2001-07-20 16:54 ` Richard Henderson
2001-07-20 17:06 ` Joern Rennecke
2001-07-20 15:27 ` Richard Henderson [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=20010720152737.B3659@redhat.com \
--to=rth@redhat.com \
--cc=Stephen.Clarke@st.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.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).