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 tree-optimization/97964] Missed optimization opportunity for VRP Date: Tue, 24 Nov 2020 09:38:04 +0000 [thread overview] Message-ID: <bug-97964-4-0qVnGUKpuA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97964-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97964 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Note, trunk handles it fine again starting with r11-4755-g22984f3f090921b5ac80ec0057f6754ec458e97e So I guess we should just add the testcase (perhaps use a parameter instead of volatile etc.) and close, ranger is not backportable and even smaller VRP improvements might be too risky.
next prev parent reply other threads:[~2020-11-24 9:38 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-24 7:47 [Bug tree-optimization/97964] New: " ishiura-compiler at ml dot kwansei.ac.jp 2020-11-24 8:06 ` [Bug tree-optimization/97964] " pinskia at gcc dot gnu.org 2020-11-24 8:27 ` rguenth at gcc dot gnu.org 2020-11-24 9:32 ` jakub at gcc dot gnu.org 2020-11-24 9:38 ` jakub at gcc dot gnu.org [this message] 2020-11-24 9:39 ` rguenth at gcc dot gnu.org 2020-11-24 9:44 ` cvs-commit at gcc dot gnu.org 2020-11-24 9:51 ` jakub at gcc dot gnu.org 2021-08-14 22:29 ` pinskia 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-97964-4-0qVnGUKpuA@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).