public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112303] [14 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: verify_flow_info failed since r14-3459-g0c78240fd7d519 Date: Tue, 31 Oct 2023 05:15:27 +0000 [thread overview] Message-ID: <bug-112303-4-5NlDOGBXSY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112303-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112303 Sam James <sjames at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs-bisection | CC| |hubicka at gcc dot gnu.org Summary|[14 Regression] ICE on |[14 Regression] ICE on |valid code at -O3 on |valid code at -O3 on |x86_64-linux-gnu: |x86_64-linux-gnu: |verify_flow_info failed |verify_flow_info failed | |since | |r14-3459-g0c78240fd7d519 --- Comment #4 from Sam James <sjames at gcc dot gnu.org> --- bisect says: commit 0c78240fd7d519fc27ca822f66a92f85edf43f70 Author: Jan Hubicka <jh@suse.cz> Date: Thu Aug 24 15:10:46 2023 +0200 Check that passes do not forget to define profile in r14-3459-g0c78240fd7d519. It's probably been there for a while. This has popped up in a bunch of places naturally.
next prev parent reply other threads:[~2023-10-31 5:15 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-30 21:52 [Bug tree-optimization/112303] New: ICE on valid code at -O3 on x86_64-linux-gnu: verify_flow_info failed zhendong.su at inf dot ethz.ch 2023-10-30 21:55 ` [Bug tree-optimization/112303] " zhendong.su at inf dot ethz.ch 2023-10-30 21:59 ` [Bug tree-optimization/112303] [14 Regression] " pinskia at gcc dot gnu.org 2023-10-30 22:00 ` pinskia at gcc dot gnu.org 2023-10-31 3:21 ` sjames at gcc dot gnu.org 2023-10-31 5:15 ` sjames at gcc dot gnu.org [this message] 2023-10-31 8:45 ` [Bug tree-optimization/112303] [14 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: verify_flow_info failed since r14-3459-g0c78240fd7d519 rguenth at gcc dot gnu.org 2023-10-31 11:08 ` zhendong.su at inf dot ethz.ch 2023-12-05 22:55 ` pinskia at gcc dot gnu.org 2023-12-05 23:02 ` jakub at gcc dot gnu.org 2023-12-06 7:35 ` rguenther at suse dot de 2024-03-05 11:19 ` jakub at gcc dot gnu.org 2024-03-26 10:36 ` rguenth at gcc dot gnu.org 2024-03-26 10:40 ` jakub at gcc dot gnu.org 2024-03-26 11:45 ` jakub at gcc dot gnu.org 2024-03-27 14:35 ` jakub at gcc dot gnu.org 2024-03-27 17:46 ` hubicka at ucw dot cz 2024-03-28 14:05 ` cvs-commit at gcc dot gnu.org 2024-03-30 3:55 ` cvs-commit at gcc dot gnu.org 2024-04-03 11:59 ` jakub 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-112303-4-5NlDOGBXSY@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).