From: "Richard Guenther" <richard.guenther@gmail.com>
To: "Zdenek Dvorak" <rakdver@kam.mff.cuni.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch] Fix gimple type checking errors on ppc
Date: Fri, 27 Jul 2007 13:25:00 -0000 [thread overview]
Message-ID: <84fc9c000707270429p60cb41e2ic4ab1ac722f18a1e@mail.gmail.com> (raw)
In-Reply-To: <20070727103731.GA14249@kam.mff.cuni.cz>
On 7/27/07, Zdenek Dvorak <rakdver@kam.mff.cuni.cz> wrote:
> Hello,
>
> build of gcc on ppc and ppc64 is failing for me with gimple type
> checking messages. The problem is in the code generated by
> rs6000_gimplify_va_arg, when TREE_TYPE (reg) is not compatible with
> sizetype.
>
> Bootstrapped & regtested on {ppc, ppc64}-linux.
Ok, thanks.
Richard.
> Zdenek
>
> * config/rs6000/rs6000.c (rs6000_gimplify_va_arg): Generate the
> operands with compatible type.
>
> Index: config/rs6000/rs6000.c
> ===================================================================
> *** config/rs6000/rs6000.c (revision 126959)
> --- config/rs6000/rs6000.c (working copy)
> *************** rs6000_gimplify_va_arg (tree valist, tre
> *** 6465,6471 ****
> {
> regalign = 1;
> u = build2 (BIT_AND_EXPR, TREE_TYPE (reg), reg,
> ! size_int (n_reg - 1));
> u = build2 (POSTINCREMENT_EXPR, TREE_TYPE (reg), reg, u);
> }
> /* _Decimal128 is passed in even/odd fpr pairs; the stored
> --- 6465,6471 ----
> {
> regalign = 1;
> u = build2 (BIT_AND_EXPR, TREE_TYPE (reg), reg,
> ! build_int_cst (TREE_TYPE (reg), n_reg - 1));
> u = build2 (POSTINCREMENT_EXPR, TREE_TYPE (reg), reg, u);
> }
> /* _Decimal128 is passed in even/odd fpr pairs; the stored
> *************** rs6000_gimplify_va_arg (tree valist, tre
> *** 6487,6493 ****
> if (sav_ofs)
> t = build2 (POINTER_PLUS_EXPR, ptr_type_node, sav, size_int (sav_ofs));
>
> ! u = build2 (POSTINCREMENT_EXPR, TREE_TYPE (reg), reg, size_int (n_reg));
> u = fold_convert (sizetype, u);
> u = build2 (MULT_EXPR, sizetype, u, size_int (sav_scale));
> t = build2 (POINTER_PLUS_EXPR, ptr_type_node, t, u);
> --- 6487,6494 ----
> if (sav_ofs)
> t = build2 (POINTER_PLUS_EXPR, ptr_type_node, sav, size_int (sav_ofs));
>
> ! u = build2 (POSTINCREMENT_EXPR, TREE_TYPE (reg), reg,
> ! build_int_cst (TREE_TYPE (reg), n_reg));
> u = fold_convert (sizetype, u);
> u = build2 (MULT_EXPR, sizetype, u, size_int (sav_scale));
> t = build2 (POINTER_PLUS_EXPR, ptr_type_node, t, u);
>
prev parent reply other threads:[~2007-07-27 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 11:00 Zdenek Dvorak
2007-07-27 13:25 ` Richard Guenther [this message]
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=84fc9c000707270429p60cb41e2ic4ab1ac722f18a1e@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rakdver@kam.mff.cuni.cz \
/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).