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 tree-optimization/100781] [12 Regression] Emitted binary code changes when -g is enabled at -O2 Date: Wed, 14 Jul 2021 21:58:33 +0000 [thread overview] Message-ID: <bug-100781-4-P6DqvheQWN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100781-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100781 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>: https://gcc.gnu.org/g:263a7e20c88a35bdfaebfac3c9abb313c5867590 commit r11-8747-g263a7e20c88a35bdfaebfac3c9abb313c5867590 Author: Andrew MacLeod <amacleod@redhat.com> Date: Tue Jun 8 09:43:17 2021 -0400 Don't process lookups for debug statements in Ranger. Although PR 100781 is not an issue in GCC11, its possible that a similar situation may arise. The identical fix cannot be easily introduced. With EVRP always running in hybrid mode, there is no need for ranger to spawn a lookup for a debug statement in this release. * gimple-range.cc (gimple_ranger::range_of_expr): Treat debug statments as contextless queries to avoid additional lookups.
prev parent reply other threads:[~2021-07-14 21:58 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-26 21:12 [Bug tree-optimization/100781] New: " tlwang at uwaterloo dot ca 2021-05-26 21:30 ` [Bug tree-optimization/100781] [12 Regression] " pinskia at gcc dot gnu.org 2021-05-26 21:31 ` pinskia at gcc dot gnu.org 2021-05-26 21:33 ` pinskia at gcc dot gnu.org 2021-05-26 21:38 ` pinskia at gcc dot gnu.org 2021-05-27 6:20 ` aldyh at gcc dot gnu.org 2021-05-27 18:13 ` amacleod at redhat dot com 2021-06-01 1:32 ` cvs-commit at gcc dot gnu.org 2021-06-01 1:36 ` amacleod at redhat dot com 2021-06-01 1:36 ` amacleod at redhat dot com 2021-07-14 21:58 ` cvs-commit at gcc dot gnu.org [this message]
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-100781-4-P6DqvheQWN@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).