This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: avx register variables

From: Ian Lance Taylor <iant at google dot com>
To: GÃbor Buella <gbuella at gmail dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Sun, 03 Jun 2012 22:45:02 -0700
Subject: Re: avx register variables
References: <CAC-8AYx7O+sT62QbS7QDbYHttX2nHd2aEeb1f1fTRP_GvrNAhA@mail.gmail.com> <alpine.DEB.2.02.1206022048290.13582@laptop-mg.saclay.inria.fr> <CAC-8AYxk1SUuN4fD5a0MKH+rKx7LdWbhsPuNT5FO2ZBaNeotaA@mail.gmail.com>

GÃbor Buella <gbuella@gmail.com> writes:

> register unsigned int something __asm__("xmm2") __attribute__
> ((__vector_size__ (32)));
>
> It seems to work, and also found out, that if I use -mno-vzeroupper ,
> I wont always lose the upper bits.
>
> BTW, I'm no expert in assembly at all, I can't figure out why is it
> XMM , why not YMM ?

Well, they are the same registers, after all.

Still, GCC ought to accept the YMM names.  Please file a bug report at
http://gcc.gnu.org/bugzilla/ for this.  Thanks.

Ian

References:
- avx register variables
  - From: Gábor Buella
- Re: avx register variables
  - From: Marc Glisse
- Re: avx register variables
  - From: Gábor Buella

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]