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 tree-optimization/105598] [11 Regression] Flag -O2 causes code to misbehave Date: Mon, 16 May 2022 08:47:51 +0000 [thread overview] Message-ID: <bug-105598-4-O8psp3xY5O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105598-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105598 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- r12-3918-g5b8b1522e04adc20980f396571be1929a32d148a is an optimization improvement. When backporting the change the failure goes away but it re-appears with -fdisable-tree-fre1 and can be mitigated with -fno-ipa-cp. -fdisable-tree-fre1 doesn't re-introduce the issue on trunk. Can you bisect what fixed this with -fdisable-tree-fre1?
next prev parent reply other threads:[~2022-05-16 8:47 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-13 17:49 [Bug c/105598] New: " greenfoo at u92 dot eu 2022-05-13 18:25 ` [Bug c/105598] [11 Regression] " jakub at gcc dot gnu.org 2022-05-16 8:47 ` rguenth at gcc dot gnu.org [this message] 2022-05-16 8:59 ` [Bug tree-optimization/105598] " jakub at gcc dot gnu.org 2022-05-16 9:18 ` rguenth at gcc dot gnu.org 2022-05-16 10:06 ` rguenth 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-105598-4-O8psp3xY5O@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).