public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jeremy.bennett at embecosm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110989] RISC-V vector ICE due to invalid tree code in GIMPLE vect pass
Date: Mon, 14 Aug 2023 14:51:00 +0000 [thread overview]
Message-ID: <bug-110989-4-OkAduk15eE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110989-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110989
Jeremy Bennett <jeremy.bennett at embecosm dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Jeremy Bennett <jeremy.bennett at embecosm dot com> ---
Confirmed the patch resolves this issue.
next prev parent reply other threads:[~2023-08-14 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 9:59 [Bug middle-end/110989] New: " jeremy.bennett at embecosm dot com
2023-08-11 11:33 ` [Bug middle-end/110989] " juzhe.zhong at rivai dot ai
2023-08-11 11:34 ` juzhe.zhong at rivai dot ai
2023-08-11 21:50 ` cvs-commit at gcc dot gnu.org
2023-08-14 14:51 ` jeremy.bennett at embecosm dot com [this message]
2023-08-15 13:55 ` cvs-commit at gcc dot gnu.org
2023-09-02 3:22 ` pinskia 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-110989-4-OkAduk15eE@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).