public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/68131] missed optimization and warning for broken overflow check Date: Wed, 28 Oct 2015 12:31:00 -0000 [thread overview] Message-ID: <bug-68131-4-w1j5UtFR10@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68131-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68131 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- We indeed do not have this optimization, only A + CST CMP CST to A CMP CST' and related. Note that _9 might be negative so we also need range info for this. VRPs symbolic range stuff isn't good enough to simplify this.
next prev parent reply other threads:[~2015-10-28 12:31 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-28 11:39 [Bug rtl-optimization/68131] New: " rv at rasmusvillemoes dot dk 2015-10-28 12:19 ` [Bug tree-optimization/68131] " glisse at gcc dot gnu.org 2015-10-28 12:31 ` rguenth at gcc dot gnu.org [this message] 2015-10-28 12:59 ` glisse at gcc dot gnu.org 2021-08-29 20:18 ` pinskia at gcc dot gnu.org 2023-10-24 20:45 ` 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-68131-4-w1j5UtFR10@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).