public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113670] ICE with vectors in named registers and -fno-vect-cost-model
Date: Tue, 30 Jan 2024 16:03:16 +0000 [thread overview]
Message-ID: <bug-113670-4-eawt3SkhYu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113670-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113670
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail|13.2.0 |
--- Comment #1 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
It's difficult to say when this started because in previous releases another
ICE (PR113622) happens anyway.
next prev parent reply other threads:[~2024-01-30 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 16:00 [Bug tree-optimization/113670] New: " xry111 at gcc dot gnu.org
2024-01-30 16:03 ` xry111 at gcc dot gnu.org [this message]
2024-01-30 16:04 ` [Bug tree-optimization/113670] " xry111 at gcc dot gnu.org
2024-01-31 8:03 ` rguenth at gcc dot gnu.org
2024-01-31 9:13 ` cvs-commit at gcc dot gnu.org
2024-01-31 9:14 ` rguenth at gcc dot gnu.org
2024-03-21 13:54 ` cvs-commit 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-113670-4-eawt3SkhYu@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).