public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Remove the postincrement queue
Date: Thu, 08 Jul 2004 21:15:00 -0000	[thread overview]
Message-ID: <20040708195110.GC20150@redhat.com> (raw)
In-Reply-To: <ccjlt2$89h$1@sea.gmane.org>

On Thu, Jul 08, 2004 at 04:35:24PM +0200, Paolo Bonzini wrote:
> Unfortunately (but quite understandably), va_arg expanders are heavy 
> users of {pre,post}{in,de}crements, which means that this patch has 
> ramifications in backend code.  The obvious solution is to expand 
> preincrements and predecrements manually, and for postincrements use 
> (x+N)-N; of course the real solution would be to transition these 
> backends to using gimplifiers for va_arg: these could well use the 
> now-banned tree codes, but this is well above my abilities.

Hum.  I'm not really fond of the brief scan of the changes you
did here in the valist code.  Most of them would need reverting
to almost exactly what's there.

Why don't we take care of this first?  I'm sure the conversion
is not above your abilities.


r~

  reply	other threads:[~2004-07-08 19:51 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 [this message]
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     ` [PATCH] Remove the postincrement queue Richard Henderson
2004-07-09 11:15       ` 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=20040708195110.GC20150@redhat.com \
    --to=rth@redhat.com \
    --cc=bonzini@gnu.org \
    --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).