From: "Christopher Matthews" <chrismatthews@google.com>
To: gcc-patches@gcc.gnu.org, Diego <dnovillo@google.com>,
"Aldy Hernandez" <aldyh@redhat.com>
Subject: Re: [tuples] Fixed inconsistent iterator interface
Date: Tue, 07 Aug 2007 22:56:00 -0000 [thread overview]
Message-ID: <5794c4c80708071556x6ee1bebcu4c0567fc6ed4fffc@mail.gmail.com> (raw)
In-Reply-To: <5794c4c80708071550y4747df3ew9966b560405db4b2@mail.gmail.com>
I was confused when I saw it - thought itter was more descriptive. I
now notice that's how it is done everywhere. I'll change it back to i.
On 8/7/07, Christopher Matthews <chrismatthews@google.com> wrote:
> ops. Included some stuff from another patch I was working on. Here is an update
>
> On 8/7/07, Christopher Matthews <chrismatthews@google.com> wrote:
> > Some of the functions in the gimple statement iterator had struct
> > arguments, others had pointer arguments. Changed them to all use
> > pointers, and update all the (now much nicer looking) uses.
> >
> > Tested on gimple.exp, compile.exp, and libgcc.
> >
> > 2007-08-07 Chris Matthews <chrismatthews@google.com>
> >
> > * gimple_iterator.h (gsi_start): Changed to produce a pointer instead of
> > struct. Updated clients.
> > (gsi_last): Same.
> > (gsi_end_p): Changed to operate on a pointer instead of struct. Updated
> > clients.
> > (gsi_one_before_end_p): Same.
> > (gsi_next): Same.
> > (gsi_prev): Same.
> > (gsi_stmt): Same.
> >
> >
>
>
next prev parent reply other threads:[~2007-08-07 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 22:33 Christopher Matthews
2007-08-07 22:46 ` Diego Novillo
2007-08-07 22:50 ` Christopher Matthews
2007-08-07 22:56 ` Christopher Matthews [this message]
2007-08-07 23:07 ` Christopher Matthews
2007-08-07 23:11 ` Diego Novillo
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=5794c4c80708071556x6ee1bebcu4c0567fc6ed4fffc@mail.gmail.com \
--to=chrismatthews@google.com \
--cc=aldyh@redhat.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@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).