On 04/27/2016 05:16 PM, H.J. Lu wrote:
This works for -m32, -mx32 and -m64. OK for trunk?
Yes, thanks.
Bernd
On Wed, Apr 27, 2016 at 2:09 AM, Bernd Schmidt wrote:
> On 04/27/2016 02:10 AM, H.J. Lu wrote:
>>
>> On Tue, Apr 26, 2016 at 3:11 PM, Bernd Schmidt
>> wrote:
>>>
>>> On 04/26/2016 09:39 PM, H.J. Lu wrote:
make check-gcc RUNTESTFLAGS="--target_board='unix{-mx32}'
i386.exp=avx51
On 04/27/2016 02:10 AM, H.J. Lu wrote:
On Tue, Apr 26, 2016 at 3:11 PM, Bernd Schmidt wrote:
On 04/26/2016 09:39 PM, H.J. Lu wrote:
make check-gcc RUNTESTFLAGS="--target_board='unix{-mx32}'
i386.exp=avx512vl-vmovdqa64-1.c"
Unfortunately, that doesn't work:
/usr/include/gnu/stubs.h:13:28:
On Tue, Apr 26, 2016 at 3:11 PM, Bernd Schmidt wrote:
> On 04/26/2016 09:39 PM, H.J. Lu wrote:
>>
>> make check-gcc RUNTESTFLAGS="--target_board='unix{-mx32}'
>> i386.exp=avx512vl-vmovdqa64-1.c"
>
>
> Unfortunately, that doesn't work:
>
> /usr/include/gnu/stubs.h:13:28: fatal error: gnu/stubs-x32.
On 04/26/2016 09:39 PM, H.J. Lu wrote:
make check-gcc RUNTESTFLAGS="--target_board='unix{-mx32}'
i386.exp=avx512vl-vmovdqa64-1.c"
Unfortunately, that doesn't work:
/usr/include/gnu/stubs.h:13:28: fatal error: gnu/stubs-x32.h: No such
file or directory
compilation terminated.
Trying to follo
On Tue, Apr 26, 2016 at 12:32 PM, Bernd Schmidt wrote:
> On 04/26/2016 08:35 PM, H.J. Lu wrote:
>>
>> This
>>
>> /* { dg-final { scan-assembler-times "vmovdqa64\[
>> \\t\]+\[^\{\n\]*%ymm\[0-9\]+\[^\nxy\]*\\(.{5}(?:\n|\[ \\t\]+#)" 1 {
>> target nonpic } } } */
>>
>> fails on x32 since x32 with 32-b
On 04/26/2016 08:35 PM, H.J. Lu wrote:
This
/* { dg-final { scan-assembler-times "vmovdqa64\[
\\t\]+\[^\{\n\]*%ymm\[0-9\]+\[^\nxy\]*\\(.{5}(?:\n|\[ \\t\]+#)" 1 {
target nonpic } } } */
fails on x32 since x32 with 32-bit pointers has (%r10d) instead of
(%r10). .{5} doesn't match.
What is this
On Tue, Apr 26, 2016 at 5:26 AM, Bernd Schmidt wrote:
> On 01/29/2016 01:19 PM, Uros Bizjak wrote:
>>>
>>> * gcc.target/i386/avx512bw-vptestmb-1.c: Correct [xyz]mm register
>>> number scans.
>>> * gcc.target/i386/avx512bw-vptestmw-1.c: Likewise.
>>> * gcc.target/i386/avx512bw-vptestnmb-1.c: Likewi
On 01/29/2016 01:19 PM, Uros Bizjak wrote:
* gcc.target/i386/avx512bw-vptestmb-1.c: Correct [xyz]mm register
number scans.
* gcc.target/i386/avx512bw-vptestmw-1.c: Likewise.
* gcc.target/i386/avx512bw-vptestnmb-1.c: Likewise.
* gcc.target/i386/avx512bw-vptestnmw-1.c: Likewise.
* gcc.target/i386/a
Hello!
> * gcc.target/i386/avx512bw-vptestmb-1.c: Correct [xyz]mm register
> number scans.
> * gcc.target/i386/avx512bw-vptestmw-1.c: Likewise.
> * gcc.target/i386/avx512bw-vptestnmb-1.c: Likewise.
> * gcc.target/i386/avx512bw-vptestnmw-1.c: Likewise.
> * gcc.target/i386/avx512cd-vpbroadcastmb2q-1
This patch corrects some tests that can fail with -frename-registers.
The problems typically are of the form "xmm[0-7]+", disallowing
registers 8 and 9, and "xmm[0-9]". disallowing numbers higher than 9.
Most the patch was automatically generated, but there were some other
cases as well.
Enab
11 matches
Mail list logo