This is the mail archive of the gcc-patches@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: Use of vector instructions in memmov/memset expanding

From: Michael Zolotukhin <michael dot v dot zolotukhin at gmail dot com>
To: Uros Bizjak <ubizjak at gmail dot com>
Cc: gcc-patches at gcc dot gnu dot org, "H.J. Lu" <hjl dot tools at gmail dot com>, Richard Guenther <richard dot guenther at gmail dot com>
Date: Wed, 13 Jul 2011 16:12:21 +0400
Subject: Re: Use of vector instructions in memmov/memset expanding
References: <CAFULd4bSjVwiMxoe__VDa_XjdJLb3_Vym4kuEvwor3BKjFLn4g@mail.gmail.com>

Thanks for the remarks! Corrected patch is attached.

On 13 July 2011 12:48, Uros Bizjak <ubizjak@gmail.com> wrote:
> Hello!
>
>> Please don't use -m32/-m64 in testcases directly.
>> You should use
>>
>> /* { dg-do compile { target { ! ia32 } } } */
>>
>> for 32bit insns and
>>
>> /* { dg-do compile { target { ia32 } } } */
>>
>> for 64bit insns.
>
> Also, there is no need to add -mtune if -march is already specified.
> -mtune will follow -march.
> To scan for the %xmm register, you don't have to add -dp to compile
> flags. -dp will also dump pattern name to file, so unless you are
> looking for specific pattern name, you should omit -dp.
>
> Uros.
>

Attachment: memfunc.patch
Description: Binary data

References:
- Re: Use of vector instructions in memmov/memset expanding
  - From: Uros Bizjak

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