public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/113556] New: gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL
@ 2024-01-23 9:05 ro at gcc dot gnu.org
2024-01-23 9:06 ` [Bug target/113556] " ro at gcc dot gnu.org
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: ro at gcc dot gnu.org @ 2024-01-23 9:05 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113556
Bug ID: 113556
Summary: gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: ams at gcc dot gnu.org
Target Milestone: ---
Target: i386-pc-solaris2.11
Since their introduction on 20230222, several tests FAIL on Solaris/x86 (both
32 and 64-bit) when using a 32-bit compiler only:
FAIL: gcc.dg/vect/vect-simd-clone-16c.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-16d.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-17c.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-17d.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-18c.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-18d.c scan-tree-dump-times vect "[\\\\n\\\\r]
[^\\\\n]* = foo\\\\.simdclone" 2
The same tests PASS (again, 32 and 64-bit) when using a 64-bit compiler
instead.
I noticed that those tests have something like
/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 2 "vect"
{ target { ! { x86_64*-*-* || { i686*-*-* || aarch64*-*-* } } } } } } */
while the 32-bit Solaris/x86 triple still is i386-pc-solaris2.11. However, that
compiler defaults to -mpentium4.
Is there anything in the tests that require specific ISA extensions only
available on i686 or is this just an oversight, so we can switch them to use
i?u6 instead?
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/113556] gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL
2024-01-23 9:05 [Bug target/113556] New: gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL ro at gcc dot gnu.org
@ 2024-01-23 9:06 ` ro at gcc dot gnu.org
2024-01-24 9:39 ` ro at gcc dot gnu.org
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: ro at gcc dot gnu.org @ 2024-01-23 9:06 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113556
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |14.0
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/113556] gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL
2024-01-23 9:05 [Bug target/113556] New: gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL ro at gcc dot gnu.org
2024-01-23 9:06 ` [Bug target/113556] " ro at gcc dot gnu.org
@ 2024-01-24 9:39 ` ro at gcc dot gnu.org
2024-01-24 12:57 ` cvs-commit at gcc dot gnu.org
2024-01-24 13:01 ` ro at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: ro at gcc dot gnu.org @ 2024-01-24 9:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113556
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2024-01-24
URL| |https://gcc.gnu.org/piperma
| |il/gcc-patches/2024-January
| |/643784.html
Ever confirmed|0 |1
--- Comment #1 from Rainer Orth <ro at gcc dot gnu.org> ---
Patch posted.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/113556] gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL
2024-01-23 9:05 [Bug target/113556] New: gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL ro at gcc dot gnu.org
2024-01-23 9:06 ` [Bug target/113556] " ro at gcc dot gnu.org
2024-01-24 9:39 ` ro at gcc dot gnu.org
@ 2024-01-24 12:57 ` cvs-commit at gcc dot gnu.org
2024-01-24 13:01 ` ro at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2024-01-24 12:57 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113556
--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Rainer Orth <ro@gcc.gnu.org>:
https://gcc.gnu.org/g:b8f54195edbecd7151095f137f9ff27e1ddc8e36
commit r14-8388-gb8f54195edbecd7151095f137f9ff27e1ddc8e36
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date: Wed Jan 24 13:56:23 2024 +0100
testsuite: i386: Don't restrict gcc.dg/vect/vect-simd-clone-16c.c etc. to
i686 [PR113556]
A couple of gcc.dg/vect/vect-simd-clone-1*.c tests FAIL on 32-bit
Solaris/x86 since 20230222:
FAIL: gcc.dg/vect/vect-simd-clone-16c.c scan-tree-dump-times vect
"[\\\\n\\\\r] [^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-16d.c scan-tree-dump-times vect
"[\\\\n\\\\r] [^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-17c.c scan-tree-dump-times vect
"[\\\\n\\\\r] [^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-17d.c scan-tree-dump-times vect
"[\\\\n\\\\r] [^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-18c.c scan-tree-dump-times vect
"[\\\\n\\\\r] [^\\\\n]* = foo\\\\.simdclone" 2
FAIL: gcc.dg/vect/vect-simd-clone-18d.c scan-tree-dump-times vect
"[\\\\n\\\\r] [^\\\\n]* = foo\\\\.simdclone" 2
The problem is that the 32-bit Solaris/x86 triple still uses i386,
although gcc defaults to -mpentium4. However, the tests only handle
x86_64* and i686*, although the tests don't seem to require some
specific ISA extension not covered by vect_simd_clones.
To fix this, the tests now allow generic i?86. At the same time, I've
removed the wildcards from x86_64* and i686* since DejaGnu uses the
canonical forms.
Tested on i386-pc-solaris2.11 and i686-pc-linux-gnu.
2024-01-24 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
gcc/testsuite:
PR target/113556
* gcc.dg/vect/vect-simd-clone-16c.c: Don't wildcard x86_64 in
target specs. Allow any i?86 target instead of i686 only.
* gcc.dg/vect/vect-simd-clone-16d.c: Likewise.
* gcc.dg/vect/vect-simd-clone-17c.c: Likewise.
* gcc.dg/vect/vect-simd-clone-17d.c: Likewise.
* gcc.dg/vect/vect-simd-clone-18c.c: Likewise.
* gcc.dg/vect/vect-simd-clone-18d.c: Likewise.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/113556] gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL
2024-01-23 9:05 [Bug target/113556] New: gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL ro at gcc dot gnu.org
` (2 preceding siblings ...)
2024-01-24 12:57 ` cvs-commit at gcc dot gnu.org
@ 2024-01-24 13:01 ` ro at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: ro at gcc dot gnu.org @ 2024-01-24 13:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113556
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Assignee|unassigned at gcc dot gnu.org |ro at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #3 from Rainer Orth <ro at gcc dot gnu.org> ---
Mine, fixed for GCC 14.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-01-24 13:01 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-01-23 9:05 [Bug target/113556] New: gcc.dg/vect/vect-simd-clone-16c.c etc. FAIL ro at gcc dot gnu.org
2024-01-23 9:06 ` [Bug target/113556] " ro at gcc dot gnu.org
2024-01-24 9:39 ` ro at gcc dot gnu.org
2024-01-24 12:57 ` cvs-commit at gcc dot gnu.org
2024-01-24 13:01 ` ro at gcc dot gnu.org
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).