From: Diego Novillo <dnovillo@google.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
amacleod@redhat.com, gcc-patches@gcc.gnu.org, jh@suse.cz
Subject: Re: [tuples] add works_with_tuples_p flag to tree_opt_pass
Date: Fri, 27 Jul 2007 17:19:00 -0000 [thread overview]
Message-ID: <46AA270C.3030104@google.com> (raw)
In-Reply-To: <20070727170325.GA3879@redhat.com>
On 7/27/07 1:03 PM, Aldy Hernandez wrote:
>> How about using properties instead since this is going away and would
>> be easier to remove?
>>
>> Some thing like PROP_NON_TUPLES.
>
> Well, mostly because I've already coded it, and my RSI didn't like it
> too much. But patches are very welcome!
It would be the same amount of changes and since it's something that
will not survive the merge, I don't think it matters much. But if
someone wants to change it, sure.
Aldy has already made it a little bit merge-proof by putting the ',' on
the new line. Thanks for that, btw.
prev parent reply other threads:[~2007-07-27 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 14:28 Aldy Hernandez
2007-07-27 16:42 ` Andrew Pinski
2007-07-27 17:16 ` Aldy Hernandez
2007-07-27 17:19 ` Diego Novillo [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=46AA270C.3030104@google.com \
--to=dnovillo@google.com \
--cc=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=pinskia@gmail.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).