public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/114190] [14 regression] Wrong code with -O2 -fno-dce -fharden-compares -mvpclmulqdq --param=max-rtl-if-conversion-unpredictable-cost=136 Date: Tue, 05 Mar 2024 09:19:36 +0000 [thread overview] Message-ID: <bug-114190-4-KZC4gXnHjj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114190-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114190 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 57611 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57611&action=edit gcc14-pr114190.patch Untested fix. After removing the REG_DEAD/REG_UNUSED notes the pass calls df_analyze, but as problems are normally only removed during df_finish_pass, the note problem is still requested and the df_analyze recreates the notes again. We could just move the df_analyze before the manual note removal, but I think it is a waste of time to compute the notes again there.
next prev parent reply other threads:[~2024-03-05 9:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-01 12:11 [Bug tree-optimization/114190] New: wrong " zsojka at seznam dot cz 2024-03-01 20:58 ` [Bug target/114190] " pinskia at gcc dot gnu.org 2024-03-01 21:04 ` pinskia at gcc dot gnu.org 2024-03-01 21:08 ` [Bug rtl-optimization/114190] " pinskia at gcc dot gnu.org 2024-03-04 8:10 ` [Bug rtl-optimization/114190] [14 regression] Wrong " rguenth at gcc dot gnu.org 2024-03-04 13:19 ` rguenth at gcc dot gnu.org 2024-03-05 8:02 ` jakub at gcc dot gnu.org 2024-03-05 9:19 ` jakub at gcc dot gnu.org [this message] 2024-03-06 8:36 ` cvs-commit at gcc dot gnu.org 2024-03-06 8:37 ` 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-114190-4-KZC4gXnHjj@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).