public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: gcc-patches@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, Yossi Markovich <YOSSIM@il.ibm.com>
Subject: Re: [RFA/RFT] Tree-level lowering of generic vectors, part 4
Date: Mon, 02 Aug 2004 07:45:00 -0000	[thread overview]
Message-ID: <410DF1DD.6030002@gnu.org> (raw)
In-Reply-To: <20040726214302.GA15536@redhat.com>

Richard Henderson wrote:

> On Fri, Jul 23, 2004 at 05:30:15PM +0200, Paolo Bonzini wrote:
> 
>>	* config/rs6000/rs6000.c (USE_ALTIVEC_FOR_ARG_P,
>>	init_cumulative_args, function_arg_boundary,
>>	function_arg_advance, function_arg,
>>	rs6000_pass_by_reference, rs6000_gimplify_va_arg):
>>	Look into the type instead of using
>>	ALTIVEC_VECTOR_MODE.
> 
> An rs6000 maintainer should review this to be sure that all vector types
> of a given width should be treated identically.

My rationale here was that SPE vectors are all exactly 8-byte wide, 
while Altivec vectors are all exactly 16-byte wide.

>>	* config/i386/i386.c (function_arg): Always treat 8-
>>	and 16-byte wide vectors the same, even if MMX/SSE
>>	are disabled.
>> 	(contains_128bit_aligned_vector_p): Add comment.
> 
> Applied.

Thanks.

Paolo

WARNING: multiple messages have this Message-ID

From: Paolo Bonzini <bonzini@gnu.org>
To: Richard Henderson <rth@redhat.com>
Cc: gcc-patches@gcc.gnu.org, Yossi Markovich <YOSSIM@il.ibm.com>
Subject: Re: [RFA/RFT] Tree-level lowering of generic vectors, part 4
Date: Mon, 02 Aug 2004 08:11:00 -0000	[thread overview]
Message-ID: <410DF1DD.6030002@gnu.org> (raw)
Message-ID: <20040802081100.OGi3BBv-pcvqmNKS6JpjQ6swx0EXC4qlAx2W-qD8eJw@z> (raw)
In-Reply-To: <20040726214302.GA15536@redhat.com>

Richard Henderson wrote:

> On Fri, Jul 23, 2004 at 05:30:15PM +0200, Paolo Bonzini wrote:
> 
>>	* config/rs6000/rs6000.c (USE_ALTIVEC_FOR_ARG_P,
>>	init_cumulative_args, function_arg_boundary,
>>	function_arg_advance, function_arg,
>>	rs6000_pass_by_reference, rs6000_gimplify_va_arg):
>>	Look into the type instead of using
>>	ALTIVEC_VECTOR_MODE.
> 
> An rs6000 maintainer should review this to be sure that all vector types
> of a given width should be treated identically.

My rationale here was that SPE vectors are all exactly 8-byte wide, 
while Altivec vectors are all exactly 16-byte wide.

>>	* config/i386/i386.c (function_arg): Always treat 8-
>>	and 16-byte wide vectors the same, even if MMX/SSE
>>	are disabled.
>> 	(contains_128bit_aligned_vector_p): Add comment.
> 
> Applied.

Thanks.

Paolo

  reply	other threads:[~2004-08-02  7:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 18:39 [RFC/RFT] Tree-level lowering of generic vectors (take 2) Yossi Markovich
2004-07-22 20:49 ` Paolo Bonzini
2004-07-23  6:36   ` Richard Henderson
2004-07-23 22:03     ` [RFA/RFT] Tree-level lowering of generic vectors, part 4 Paolo Bonzini
2004-07-27  0:59       ` Richard Henderson
2004-08-02  7:45         ` Paolo Bonzini [this message]
2004-08-02  8:11           ` Paolo Bonzini
2004-10-06 19:47       ` David Edelsohn
2004-10-07 14:45         ` Paolo Bonzini
2004-10-18  1:58           ` David Edelsohn
2004-10-21 10:01             ` [PATCH] PR/17836 (was Re: [RFA/RFT] Tree-level lowering of generic vectors, part 4) Paolo Bonzini
2004-10-22 21:14               ` David Edelsohn
2004-07-28 19:12 [RFA/RFT] Tree-level lowering of generic vectors, part 4 Yossi Markovich

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=410DF1DD.6030002@gnu.org \
    --to=bonzini@gnu.org \
    --cc=YOSSIM@il.ibm.com \
    --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).