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 middle-end/112344] [14 Regression] Wrong code at -O2 on x86_64-pc-linux-gnu Date: Wed, 22 Nov 2023 09:10:26 +0000 [thread overview] Message-ID: <bug-112344-4-yXHpetwkOo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112344-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112344 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- thread2 comes along and threads the e_1 <= 19 jump from the entry "twice", resulting in bogus ranges to be used? Checking profitability of path (backwards): bb:3 (2 insns) bb:9 (0 insns) (latch) bb:5 (3 insns) bb:4 Control statement insns: 2 Overall: 3 insns Registering killing_def (path_oracle) e_43 Registering killing_def (path_oracle) _37 Registering killing_def (path_oracle) _42 Registering killing_def (path_oracle) _41 Registering killing_def (path_oracle) _40 Registering killing_def (path_oracle) _39 Registering killing_def (path_oracle) _38 Checking profitability of path (backwards): [3] Registering jump thread: (4, 5) incoming edge; (5, 9) normal (9, 3) normal (back) (3, 4) nocopy; path: 4->5->9->3->4 SUCCESS
next prev parent reply other threads:[~2023-11-22 9:10 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-02 6:30 [Bug middle-end/112344] New: " jwzeng at nuaa dot edu.cn 2023-11-02 6:41 ` [Bug middle-end/112344] " pinskia at gcc dot gnu.org 2023-11-02 6:42 ` pinskia at gcc dot gnu.org 2023-11-02 6:47 ` jwzeng at nuaa dot edu.cn 2023-11-02 6:49 ` pinskia at gcc dot gnu.org 2023-11-02 10:06 ` rguenth at gcc dot gnu.org 2023-11-21 19:22 ` jakub at gcc dot gnu.org 2023-11-21 19:23 ` jakub at gcc dot gnu.org 2023-11-22 7:43 ` rguenth at gcc dot gnu.org 2023-11-22 9:10 ` rguenth at gcc dot gnu.org [this message] 2023-11-22 10:06 ` rguenth at gcc dot gnu.org 2023-11-22 14:40 ` cvs-commit at gcc dot gnu.org 2023-11-22 14:41 ` rguenth at gcc dot gnu.org 2023-11-24 7:50 ` cvs-commit at gcc dot gnu.org 2024-02-18 10:07 ` cvs-commit 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-112344-4-yXHpetwkOo@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).