public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97104] [11 Regression] aarch64, SVE: ICE in vect_get_loop_mask since r11-3070-g783dc66f9cc
Date: Tue, 09 Mar 2021 14:24:02 +0000 [thread overview]
Message-ID: <bug-97104-4-V2vlVeJswH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97104-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97104
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org,
| |rsandifo at gcc dot gnu.org
Keywords| |needs-bisection
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Also gone latent (or fixed) now. I also know nothing about the loop masks
code.
Extracting a GIMPLE testcase from one of the broken revs maybe carries this
over.
We're vectorizing the last testcase with SVE now and not ICEing. So maybe it
was really fixed, who knows (but I don't see any live stmts).
Can somebody bisect what fixed this?
next prev parent reply other threads:[~2021-03-09 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 11:19 [Bug tree-optimization/97104] New: " acoplan at gcc dot gnu.org
2020-09-18 11:20 ` [Bug tree-optimization/97104] " acoplan at gcc dot gnu.org
2020-09-18 12:04 ` rguenth at gcc dot gnu.org
2020-10-16 12:09 ` rguenth at gcc dot gnu.org
2020-11-05 9:49 ` acoplan at gcc dot gnu.org
2020-12-10 17:00 ` akrl at gcc dot gnu.org
2021-01-14 16:13 ` acoplan at gcc dot gnu.org
2021-03-09 14:24 ` rguenth at gcc dot gnu.org [this message]
2021-03-09 14:25 ` acoplan at gcc dot gnu.org
2021-03-09 14:57 ` acoplan 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-97104-4-V2vlVeJswH@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).