From: Paolo Bonzini <paolo.bonzini@polimi.it>
To: Paolo Bonzini <paolo.bonzini@polimi.it>
Cc: Richard Henderson <rth@redhat.com>,
Paolo Bonzini <bonzini@gnu.org>,
gcc-patches@gcc.gnu.org
Subject: [RFT/RFA] gimplify pa va_arg
Date: Fri, 09 Jul 2004 09:43:00 -0000 [thread overview]
Message-ID: <40EE6551.6090603@polimi.it> (raw)
In-Reply-To: <40EE4596.1090008@polimi.it>
And here is the second. This gives several differences for both PA and
PA64 in the struct case. For PA64, it looks like awful optimization on
part of the current mainline GCC (but HPPA assembly is not my forte).
For PA, the only important change is that the frame grows from 64 to 128
bytes, but again I cannot figure it out.
I attach two sdiffs to help review.
Ok for mainline?
Paolo
2004-07-09 Paolo Bonzini <bonzini@gnu.org>
* config/pa/pa.h (EXPAND_BUILTIN_VA_ARG): Do not define.
* config/pa/pa.c (hppa_gimplify_va_arg_expr): New, based on
hppa_va_arg. Produce GIMPLE in the pre-queue instead of
expanding trees to RTL.
next prev parent reply other threads:[~2004-07-09 9:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 14:55 [PATCH] Remove the postincrement queue 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 ` Paolo Bonzini [this message]
2004-07-09 9:44 ` [RFT/RFA] gimplify pa va_arg 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
2004-07-09 20:48 [RFT/RFA] gimplify pa va_arg John David Anglin
[not found] <no.id>
2004-07-09 21:01 ` John David Anglin
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=40EE6551.6090603@polimi.it \
--to=paolo.bonzini@polimi.it \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.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).