public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106737] [13 Regression] ICE: verify_ssa failed (error: stmt with wrong VUSE) Date: Sat, 27 Aug 2022 07:28:55 +0000 [thread overview] Message-ID: <bug-106737-4-VJerHBvBiq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106737-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106737 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:4d291ca6a48eeeef3f51b8ab8452fe2166f021ee commit r13-2235-g4d291ca6a48eeeef3f51b8ab8452fe2166f021ee Author: Jakub Jelinek <jakub@redhat.com> Date: Sat Aug 27 09:28:02 2022 +0200 Require fgraphite effective target for pr106737.c test [PR106737] The test uses -floop-parallelize-all which emits a sorry when graphite isn't configured in. 2022-08-27 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/106737 * gcc.dg/autopar/pr106737.c: Require fgraphite effective target.
prev parent reply other threads:[~2022-08-27 7:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-25 6:08 [Bug tree-optimization/106737] New: " asolokha at gmx dot com 2022-08-25 8:31 ` [Bug tree-optimization/106737] " rguenth at gcc dot gnu.org 2022-08-25 8:42 ` rguenth at gcc dot gnu.org 2022-08-25 8:45 ` cvs-commit at gcc dot gnu.org 2022-08-25 8:45 ` rguenth at gcc dot gnu.org 2022-08-27 7:28 ` cvs-commit 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-106737-4-VJerHBvBiq@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: linkBe 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).