From: Steven Bosscher <steven@gcc.gnu.org>
To: law@redhat.com, Jan Hubicka <hubicka@ucw.cz>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
gcc-patches@gcc.gnu.org, dnovillo@redhat.com
Subject: Re: [RFC] Use accessor macros for the head and end of a basic block
Date: Tue, 09 Dec 2003 06:52:00 -0000 [thread overview]
Message-ID: <200312090749.12424.steven@gcc.gnu.org> (raw)
In-Reply-To: <200312090405.hB945g4m016730@speedy.slc.redhat.com>
On Tuesday 09 December 2003 05:05, law@redhat.com wrote:
> I would _strongly_ recommend this go into the mainline first
Of course. Where did I say [tree-ssa] in the subject line?
I take it you do not dislike the idea of putting this kind of patch on
mainline in this stage?
Gr.
Steven
next prev parent reply other threads:[~2003-12-09 6:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 15:33 Why are BLOCK_HEAD/BLOCK_END not used? Steven Bosscher
2003-12-08 22:09 ` [RFC] Use accessor macros for the head and end of a basic block Steven Bosscher
2003-12-08 22:35 ` Jan Hubicka
2003-12-09 5:04 ` law
2003-12-09 6:52 ` Steven Bosscher [this message]
2003-12-09 9:28 ` law
2003-12-10 8:47 ` Steven Bosscher
2003-12-10 22:49 ` Zack Weinberg
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=200312090749.12424.steven@gcc.gnu.org \
--to=steven@gcc.gnu.org \
--cc=dnovillo@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).