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/107153] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 Date: Mon, 10 Oct 2022 10:05:55 +0000 [thread overview] Message-ID: <bug-107153-4-9AI2z1Vy0Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107153-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107153 --- 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:a99f511c57b5b02edfd5969148c580b4a8737ee8 commit r13-3191-ga99f511c57b5b02edfd5969148c580b4a8737ee8 Author: Jakub Jelinek <jakub@redhat.com> Date: Mon Oct 10 12:04:56 2022 +0200 Require fgraphite effective target for pr107153.c test [PR107153] The test uses -floop-parallelize-all which emits a sorry when graphite isn't configured in. 2022-10-10 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/107153 * gcc.dg/autopar/pr107153.c: Require fgraphite effective target.
prev parent reply other threads:[~2022-10-10 10:05 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-04 13:04 [Bug tree-optimization/107153] New: " asolokha at gmx dot com 2022-10-04 13:12 ` [Bug tree-optimization/107153] " marxin at gcc dot gnu.org 2022-10-06 10:13 ` rguenth at gcc dot gnu.org 2022-10-07 8:29 ` rguenth at gcc dot gnu.org 2022-10-07 12:27 ` cvs-commit at gcc dot gnu.org 2022-10-07 12:28 ` rguenth at gcc dot gnu.org 2022-10-10 10:05 ` 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-107153-4-9AI2z1Vy0Z@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).