public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103041] [12 regression] gcc.dg/vect/slp-reduc-10a.c etc. FAIL
Date: Tue, 02 Nov 2021 18:50:26 +0000 [thread overview]
Message-ID: <bug-103041-4-e1dQeLC9v7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103041-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103041
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from luoxhu at gcc dot gnu.org ---
> Could you please verify whether it is caused by r12-4818 instead of r12-4819?
> r12-4819 is a NFC patch which seems more unlikely, and r12-4818 also ICEs in
> PR103029, it is possibly a duplicate of that.
>
>
> commit f35af8df241a9eb9c2edf7da26d3c5f53d6e2511
> Author: Xionghu Luo <luoxhu@linux.ibm.com>
> Date: Mon Nov 1 00:12:36 2021 -0500
>
> Refactor loop_version
It is indeed r12-4818 that introduced the failures on sparc.
next prev parent reply other threads:[~2021-11-02 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 9:42 [Bug tree-optimization/103041] New: " ro at gcc dot gnu.org
2021-11-02 9:43 ` [Bug tree-optimization/103041] " ro at gcc dot gnu.org
2021-11-02 12:10 ` luoxhu at gcc dot gnu.org
2021-11-02 16:08 ` rguenth at gcc dot gnu.org
2021-11-02 17:50 ` rguenth at gcc dot gnu.org
2021-11-02 18:50 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2021-11-03 1:22 ` luoxhu 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-103041-4-e1dQeLC9v7@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).