From: Richard Henderson <rth@redhat.com>
To: Paolo Bonzini <paolo.bonzini@polimi.it>
Cc: Paolo Bonzini <bonzini@gnu.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Remove the postincrement queue
Date: Fri, 09 Jul 2004 10:55:00 -0000 [thread overview]
Message-ID: <20040709101454.GA8047@redhat.com> (raw)
In-Reply-To: <40EE4596.1090008@polimi.it>
On Fri, Jul 09, 2004 at 09:13:26AM +0200, Paolo Bonzini wrote:
> Would you preapprove the other bits for when the gimple_va_arg
> conversion is done?
I'd like to see if we can get rid of the rest of the
expand_increment calls.
r~
next prev parent reply other threads:[~2004-07-09 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 14:55 Paolo Bonzini
2004-07-08 21:15 ` Richard Henderson
2004-07-09 8:34 ` Paolo Bonzini
2004-07-09 9:38 ` gimplify mn10300 va_arg Paolo Bonzini
2004-07-09 11:10 ` Richard Henderson
2004-07-09 9:43 ` [RFT/RFA] gimplify pa va_arg Paolo Bonzini
2004-07-09 9:44 ` Paolo Bonzini
2004-07-09 10:08 ` Paolo Bonzini
2004-07-09 10:13 ` Paolo Bonzini
2004-07-09 10:55 ` Richard Henderson [this message]
2004-07-09 11:15 ` [PATCH] Remove the postincrement queue Paolo Bonzini
2004-07-09 15:49 ` [PATCH] Remove the postincrement queue, take 2 Paolo Bonzini
2004-07-09 22:05 ` Richard Henderson
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=20040709101454.GA8047@redhat.com \
--to=rth@redhat.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paolo.bonzini@polimi.it \
/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).