From: Janis Johnson <janis187@us.ibm.com>
To: Bob Wilson <bwilson@tensilica.com>
Cc: rth@redhat.com, gcc@gcc.gnu.org
Subject: Re: [cft] subreg validation round 2
Date: Wed, 17 Nov 2004 22:32:00 -0000 [thread overview]
Message-ID: <20041117223128.GA6565@us.ibm.com> (raw)
In-Reply-To: <419BA411.5090801@tensilica.com>
On Wed, Nov 17, 2004 at 11:18:41AM -0800, Bob Wilson wrote:
>
> But speaking of picking up pieces after the fact....
>
> Your change to assign_parm_setup_block() on 2004-11-13 is causing/exposing
> a problem for Xtensa targets. Specifically, this piece:
>
> *************** assign_parm_setup_block (tree parm, stru
> *** 2648,2654 ****
...
>
> The Xtensa FUNCTION_ARG macro is returning a BLKmode REG for a 3-byte
> struct argument. This used to be converted to an SImode REG, but now it
> gets passed to gen_lowpart, which barfs on the BLKmode argument.
That change also causes several new test failures for powerpc64-linux
with -m64, which now ICE in gen_lowpart_common for a BLKmode argument.
Janis
next prev parent reply other threads:[~2004-11-17 22:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 18:58 Richard Henderson
2004-11-17 19:20 ` Bob Wilson
2004-11-17 19:58 ` Richard Henderson
2004-11-18 1:06 ` Alan Modra
2004-11-18 2:43 ` Bob Wilson
2004-11-18 16:23 ` Richard Sandiford
2004-11-19 21:39 ` Richard Henderson
2004-11-22 20:40 ` Richard Henderson
2004-11-17 22:32 ` Janis Johnson [this message]
2004-11-17 23:05 ` Andrew Pinski
2004-11-18 11:40 ` Alan Modra
2004-11-17 19:46 ` Eric Botcazou
2004-11-19 21:50 ` Richard Henderson
2004-11-19 22:43 ` Eric Botcazou
2004-11-19 22:46 ` Richard Henderson
2004-11-18 23:43 ` Kaz Kojima
2004-11-19 0:08 ` Janis Johnson
2004-11-17 19:19 Ulrich Weigand
[not found] <OF12E4E5CC.BDFB0F1C-ON41256F4F.0067F055-41256F4F.00682968@LocalDomain>
2004-11-17 21:42 ` Ulrich Weigand
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=20041117223128.GA6565@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=bwilson@tensilica.com \
--cc=gcc@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).