From: "Zack Weinberg" <zack@codesourcery.com>
To: Steven Bosscher <steven@gcc.gnu.org>
Cc: mark@codesourcery.com, law@redhat.com,
Jan Hubicka <hubicka@ucw.cz>,
"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: Wed, 10 Dec 2003 22:49:00 -0000 [thread overview]
Message-ID: <87he08wc7l.fsf@codesourcery.com> (raw)
In-Reply-To: <200312100857.49315.steven@gcc.gnu.org> (Steven Bosscher's message of "Wed, 10 Dec 2003 08:57:49 +0100")
Steven Bosscher <steven@gcc.gnu.org> writes:
> On Tuesday 09 December 2003 07:52, law@redhat.com wrote:
>> In message <200312090749.12424.steven@gcc.gnu.org>, Steven Bosscher writes:
>> >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?
>>
>> For mainline, I'm more than happy to leave it up to Mark :-) I've got no
>> strong opinions there.
>
> Here is the full patch for mainline, bootstrapped (c,c++,objc,f77) and
> checked on i686-pc-linux-gnu. Very mechanical, in all. I renamed the
> head and end field to make sure no-one uses it again and gets away with
> it unpunished...
>
> OK for mainline? Once it's there I'll do the same for tree-ssa.
Since Mark is out of town, since this is extremely mechanical and low
risk, and since divergence between mainline and tree-ssa is
undesirable here, I am willing to approve this patch for mainline -
but it comes right back out again if it causes the slightest bit of
trouble, capische?
zw
prev parent reply other threads:[~2003-12-10 22:16 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
2003-12-09 9:28 ` law
2003-12-10 8:47 ` Steven Bosscher
2003-12-10 22:49 ` Zack Weinberg [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=87he08wc7l.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=dnovillo@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@redhat.com \
--cc=mark@codesourcery.com \
--cc=steven@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).