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 c++/106841] [12 Regression] ICE in vect_get_vec_defs_for_operand, at tree-vect-stmts.cc:1509 since r12-2733-g31855ba6b16cd138
Date: Fri, 07 Oct 2022 06:55:30 +0000 [thread overview]
Message-ID: <bug-106841-4-o2m8kLykra@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106841-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106841
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Kenneth Hoste from comment #9)
> I seem to be running into the same problem using GCC 11.3 (when compiling
> OpenMM 7.7.0 with CUDA support). Is there a reason why the fix wasn't
> backported to GCC 11 too?
Because we don't have a testcase that fails on the GCC 11 branch. Can you
confirm that cherry-picking the fix fixes the issue you see?
prev parent reply other threads:[~2022-10-07 6:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 19:14 [Bug c++/106841] New: ice in vect_get_vec_defs_for_operand, at tree-vect-stmts.cc:1509 dcb314 at hotmail dot com
2022-09-05 19:17 ` [Bug c++/106841] " dcb314 at hotmail dot com
2022-09-05 21:17 ` dcb314 at hotmail dot com
2022-09-06 4:49 ` [Bug c++/106841] [12/13 Regression] ICE in vect_get_vec_defs_for_operand, at tree-vect-stmts.cc:1509 since r12-2733-g31855ba6b16cd138 marxin at gcc dot gnu.org
2022-09-06 8:01 ` rguenth at gcc dot gnu.org
2022-09-06 8:55 ` cvs-commit at gcc dot gnu.org
2022-09-06 9:10 ` [Bug c++/106841] [12 " rguenth at gcc dot gnu.org
2022-09-09 9:50 ` cvs-commit at gcc dot gnu.org
2022-09-09 9:50 ` rguenth at gcc dot gnu.org
2022-10-06 15:56 ` kenneth.hoste at ugent dot be
2022-10-07 6:55 ` rguenth at gcc dot gnu.org [this message]
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-106841-4-o2m8kLykra@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).