public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115152] [13/14/15 Regression] wrong code at -O3 with "-fno-tree-fre -fno-tree-dominator-opts -fno-tree-loop-im" on x86_64-linux-gnu Date: Sat, 18 May 2024 21:40:37 +0000 [thread overview] Message-ID: <bug-115152-4-M0laHMGBYF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115152-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115152 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|wrong code at -O3 with |[13/14/15 Regression] wrong |"-fno-tree-fre |code at -O3 with |-fno-tree-dominator-opts |"-fno-tree-fre |-fno-tree-loop-im" on |-fno-tree-dominator-opts |x86_64-linux-gnu |-fno-tree-loop-im" on | |x86_64-linux-gnu Target Milestone|--- |13.3
next prev parent reply other threads:[~2024-05-18 21:40 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-18 20:22 [Bug tree-optimization/115152] New: " zhendong.su at inf dot ethz.ch 2024-05-18 21:40 ` pinskia at gcc dot gnu.org [this message] 2024-05-18 21:40 ` [Bug tree-optimization/115152] [13/14/15 Regression] " pinskia at gcc dot gnu.org 2024-05-18 21:53 ` pinskia at gcc dot gnu.org 2024-05-18 21:54 ` pinskia at gcc dot gnu.org 2024-05-20 18:27 ` [Bug tree-optimization/115152] [13/14/15 Regression] wrong code at -O3 with "-fno-tree-fre -fno-tree-dominator-opts -fno-tree-loop-im" on x86_64-linux-gnu since r13-455 jakub at gcc dot gnu.org 2024-05-20 18:36 ` jakub at gcc dot gnu.org 2024-05-21 6:38 ` rguenth at gcc dot gnu.org 2024-05-21 9:20 ` jakub at gcc dot gnu.org 2024-05-21 11:57 ` jakub at gcc dot gnu.org 2024-05-22 7:14 ` cvs-commit at gcc dot gnu.org 2024-05-22 7:19 ` cvs-commit at gcc dot gnu.org 2024-05-22 7:35 ` cvs-commit at gcc dot gnu.org 2024-05-22 11:11 ` 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-115152-4-M0laHMGBYF@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).