This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Inconsistency in ordering vector widening operations on big-endian targets?
- From: Alan Modra <amodra at gmail dot com>
- To: Tejas Belagod <tbelagod at arm dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 13 Jun 2013 13:41:59 +0930
- Subject: Re: [RFC] Inconsistency in ordering vector widening operations on big-endian targets?
- References: <51B89246 dot 3010501 at arm dot com>
On Wed, Jun 12, 2013 at 04:22:46PM +0100, Tejas Belagod wrote:
> From the IR above, it seems that result of widening the high part
> (vect__12.6_40) is being stored at offset 0 from _29 and result of
> widening the low part goes into *(_29 + 16). Shouldn't this be the
> other way around?
Big-endian targets store the high part of multi-byte values at the low
address. Why should vectors be different?
--
Alan Modra
Australia Development Lab, IBM