public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103042] New: gcc.dg/vect/complex/bb-slp-complex-add-pattern-unsigned-long.c etc. FAIL
Date: Tue, 02 Nov 2021 10:00:37 +0000 [thread overview]
Message-ID: <bug-103042-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103042
Bug ID: 103042
Summary: gcc.dg/vect/complex/bb-slp-complex-add-pattern-unsigne
d-long.c etc. FAIL
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: tnfchris at gcc dot gnu.org
Target Milestone: ---
Target: sparc-sun-solaris2.11, arm-none-linux-gnueabihf
Several of the testcases modified in
commit 4045d5fa42f2ee7b284977c8f2f0edc300a63e43
Author: Tamar Christina <tamar.christina@arm.com>
Date: Fri Oct 29 12:47:39 2021 +0100
middle-end: Add target independent tests for Arm complex numbers
vectorization.
FAIL on Solaris/SPARC (32 and 64-bit) and ARM:
FAIL: gcc.dg/vect/complex/bb-slp-complex-add-pattern-unsigned-long.c -flto
-ffat-lto-objects scan-tree-dump slp1 "Found COMPLEX_ADD_ROT270"
FAIL: gcc.dg/vect/complex/bb-slp-complex-add-pattern-unsigned-long.c -flto
-ffat-lto-objects scan-tree-dump slp1 "Found COMPLEX_ADD_ROT90"
FAIL: gcc.dg/vect/complex/bb-slp-complex-add-pattern-unsigned-long.c
scan-tree-dump slp1 "Found COMPLEX_ADD_ROT270"
FAIL: gcc.dg/vect/complex/bb-slp-complex-add-pattern-unsigned-long.c
scan-tree-dump slp1 "Found COMPLEX_ADD_ROT90"
FAIL: gcc.dg/vect/complex/fast-math-bb-slp-complex-add-pattern-double.c
scan-tree-dump slp1 "Found COMPLEX_ADD_ROT270"
FAIL: gcc.dg/vect/complex/fast-math-bb-slp-complex-add-pattern-double.c
scan-tree-dump slp1 "Found COMPLEX_ADD_ROT90"
FAIL: gcc.dg/vect/complex/vect-complex-add-pattern-long.c -flto
-ffat-lto-objects scan-tree-dump vect "Found COMPLEX_ADD_ROT270"
FAIL: gcc.dg/vect/complex/vect-complex-add-pattern-long.c -flto
-ffat-lto-objects scan-tree-dump vect "Found COMPLEX_ADD_ROT90"
FAIL: gcc.dg/vect/complex/vect-complex-add-pattern-long.c scan-tree-dump vect
"Found COMPLEX_ADD_ROT270"
FAIL: gcc.dg/vect/complex/vect-complex-add-pattern-long.c scan-tree-dump vect
"Found COMPLEX_ADD_ROT90"
FAIL: gcc.dg/vect/complex/vect-complex-add-pattern-unsigned-long.c -flto
-ffat-lto-objects scan-tree-dump vect "Found COMPLEX_ADD_ROT270"
FAIL: gcc.dg/vect/complex/vect-complex-add-pattern-unsigned-long.c -flto
-ffat-lto-objects scan-tree-dump vect "Found COMPLEX_ADD_ROT90"
FAIL: gcc.dg/vect/complex/vect-complex-add-pattern-unsigned-long.c
scan-tree-dump vect "Found COMPLEX_ADD_ROT270"
FAIL: gcc.dg/vect/complex/vect-complex-add-pattern-unsigned-long.c
scan-tree-dump vect "Found COMPLEX_ADD_ROT90"
I'll attach one example dump for inspection.
next reply other threads:[~2021-11-02 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 10:00 ro at gcc dot gnu.org [this message]
2021-11-02 10:02 ` [Bug tree-optimization/103042] " ro at gcc dot gnu.org
2021-11-02 10:02 ` ro at gcc dot gnu.org
2021-11-02 10:04 ` tnfchris at gcc dot gnu.org
2021-11-04 13:00 ` [Bug testsuite/103042] " tnfchris at gcc dot gnu.org
2021-11-04 13:47 ` cvs-commit at gcc dot gnu.org
2021-11-04 13:54 ` tnfchris at gcc dot gnu.org
2021-11-05 9:33 ` ro at gcc dot gnu.org
2021-11-05 9:37 ` tnfchris at gcc dot gnu.org
2021-11-09 10:02 ` tnfchris at gcc dot gnu.org
2021-11-10 12:06 ` cvs-commit at gcc dot gnu.org
2021-11-11 12:24 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-11-11 12:26 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-11-11 13:10 ` tnfchris at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-103042-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).