public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/103432] [11 regression] libjxl-0.5 is miscompiled, works fine with -fno-ipa-modref Date: Thu, 07 Apr 2022 12:04:17 +0000 [thread overview] Message-ID: <bug-103432-4-C2vuDWQ6DS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103432-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103432 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:f0c601ed0080ab9ebe2bc0c23d41471531e2af02 commit r11-9791-gf0c601ed0080ab9ebe2bc0c23d41471531e2af02 Author: Jan Hubicka <jh@suse.cz> Date: Fri Nov 26 13:36:35 2021 +0100 Fix handling of in_flags in update_escape_summary_1 update_escape_summary_1 has thinko where it compues proper min_flags but then stores original value (ignoring the fact whether there was a dereference in the escape point). PR ipa/103432 * ipa-modref.c (update_escape_summary_1): Fix handling of min_flags. (cherry picked from commit a70faf6e4df7481c2c9a08a06657c20beb3043de)
next prev parent reply other threads:[~2022-04-07 12:04 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-25 23:59 [Bug tree-optimization/103432] New: [12 " slyfox at gcc dot gnu.org 2021-11-26 0:19 ` [Bug ipa/103432] " pinskia at gcc dot gnu.org 2021-11-26 0:31 ` [Bug tree-optimization/103432] " hubicka at gcc dot gnu.org 2021-11-26 0:33 ` [Bug ipa/103432] " pinskia at gcc dot gnu.org 2021-11-26 0:36 ` pinskia at gcc dot gnu.org 2021-11-26 7:24 ` rguenth at gcc dot gnu.org 2021-11-26 9:14 ` hubicka at kam dot mff.cuni.cz 2021-11-26 12:46 ` [Bug ipa/103432] [11 " hubicka at gcc dot gnu.org 2021-11-26 12:47 ` marxin at gcc dot gnu.org 2021-11-26 13:53 ` rguenth at gcc dot gnu.org 2021-11-26 22:45 ` slyfox at gcc dot gnu.org 2022-04-07 12:04 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-07 12:05 ` 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-103432-4-C2vuDWQ6DS@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).