From: "Andrew Pinski" <pinskia@gmail.com>
To: "Ian Lance Taylor" <iant@google.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PATCH RFC: Use type alias_set_type to hold alias sets
Date: Fri, 10 Aug 2007 00:37:00 -0000 [thread overview]
Message-ID: <de8d50360708091737j7f80de7aj50502788ac7e6fed@mail.gmail.com> (raw)
In-Reply-To: <m31weccju3.fsf@localhost.localdomain>
On 09 Aug 2007 17:30:12 -0700, Ian Lance Taylor <iant@google.com> wrote:
> To avoid the kind of error made in the original patch, in which some
> variables did not change type, this is a purely mechanical patch to
> change all alias set representations to have type alias_set_type.
I love this idea and I think we should use it more often for other
variables where we store/use in different places.
Thanks,
Andrew Pinski
next prev parent reply other threads:[~2007-08-10 0:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 0:31 Ian Lance Taylor
2007-08-10 0:37 ` Andrew Pinski [this message]
2007-08-10 16:38 ` Mark Mitchell
2007-08-10 1:45 ` Richard Kenner
2007-08-10 3:49 ` Diego Novillo
2007-08-11 17:23 ` Ian Lance Taylor
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=de8d50360708091737j7f80de7aj50502788ac7e6fed@mail.gmail.com \
--to=pinskia@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.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).