public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/115092] [14/15 Regression] wrong code at -O1 with "-fgcse -ftree-pre -fno-tree-dominator-opts -fno-tree-fre -fno-guess-branch-probability" on x86_64-linux-gnu since r14-4810 Date: Wed, 15 May 2024 11:49:58 +0000 [thread overview] Message-ID: <bug-115092-4-Dd2wFDN3Da@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115092-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115092 --- Comment #9 from Segher Boessenkool <segher at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #8) > > Yeah, that look like it is missing some test. > > I'd go with > --- gcc/combine.cc.jj 2024-05-07 18:10:10.415874636 +0200 > +++ gcc/combine.cc 2024-05-15 13:33:26.555081215 +0200 > @@ -11852,8 +11852,10 @@ simplify_compare_const (enum rtx_code co > `and'ed with that bit), we can replace this with a comparison > with zero. */ > if (const_op > - && (code == EQ || code == NE || code == GE || code == GEU > - || code == LT || code == LTU) > + && (code == EQ || code == NE || code == GEU || code == LTU > + /* This optimization is incorrect for signed >= INT_MIN or > + < INT_MIN, those are always true or always false. */ > + || ((code == GE || code == LT) && const_op > 0)) > && is_a <scalar_int_mode> (mode, &int_mode) > && GET_MODE_PRECISION (int_mode) - 1 < HOST_BITS_PER_WIDE_INT > && pow2p_hwi (const_op & GET_MODE_MASK (int_mode)) Pre-approved. Thanks! > Seems there is no canonical way to return this is always true or this is > always false, > sure, we could make up something like NE 1 0 or EQ 1 0 or similar, but it > wouldn't likely match and the question is if it would simplify. Later code will likely pick this up. More likely than with the GE anyway :-) > The const_op == -1 handling below this looks correct to me. Yup. > > That needs to be fixed of course, but independent of that, this should really > > have been completely folded away earlier already? > > It would if one wouldn't carefully disable tons of optimizations (say -O1, > so no (significant) VRP, dom* disabled, fre disabled). Ha :-)
next prev parent reply other threads:[~2024-05-15 11:49 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-14 19:05 [Bug tree-optimization/115092] New: wrong code at -O1 with "-fgcse -ftree-pre -fno-tree-dominator-opts -fno-tree-fre -fno-guess-branch-probability" on x86_64-linux-gnu zhendong.su at inf dot ethz.ch 2024-05-14 19:13 ` [Bug tree-optimization/115092] [14/15 Regression] wrong code at -O1 with "-fgcse -ftree-pre -fno-tree-dominator-opts -fno-tree-fre -fno-guess-branch-probability" on x86_64-linux-gnu since r14-4810 jakub at gcc dot gnu.org 2024-05-14 19:32 ` [Bug rtl-optimization/115092] " pinskia at gcc dot gnu.org 2024-05-14 22:04 ` pinskia at gcc dot gnu.org 2024-05-15 10:02 ` jakub at gcc dot gnu.org 2024-05-15 11:16 ` jakub at gcc dot gnu.org 2024-05-15 11:22 ` segher at gcc dot gnu.org 2024-05-15 11:32 ` segher at gcc dot gnu.org 2024-05-15 11:44 ` jakub at gcc dot gnu.org 2024-05-15 11:49 ` segher at gcc dot gnu.org [this message] 2024-05-15 12:09 ` jakub at gcc dot gnu.org 2024-05-15 13:36 ` segher at gcc dot gnu.org 2024-05-15 16:44 ` cvs-commit at gcc dot gnu.org 2024-06-04 14:26 ` cvs-commit at gcc dot gnu.org 2024-06-04 14:28 ` jakub at gcc dot gnu.org 2024-06-11 6:17 ` cvs-commit at gcc dot gnu.org 2024-06-11 10:38 ` cvs-commit at gcc dot gnu.org 2024-06-20 13:23 ` cvs-commit 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-115092-4-Dd2wFDN3Da@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).