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 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 10:02:29 +0000	[thread overview]
Message-ID: <bug-115092-4-JIe8AOhkIx@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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |segher at gcc dot gnu.org

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Indeed, combine_simplify_rtx on
(set (reg:CCGC 17 flags)
    (compare:CCGC (sign_extract:SI (reg/v:SI 101 [ g ])
            (const_int 1 [0x1])
            (const_int 0 [0]))
        (const_int -1 [0xffffffffffffffff])))
with VOIDmode, false, false remaining arguments is optimizing it to
(set (reg:CCZ 17 flags)
    (compare:CCZ (zero_extract:SI (reg/v:SI 101 [ g ])
            (const_int 1 [0x1])
            (const_int 0 [0]))
        (const_int 0 [0])))
which is ok if it would be used solely in equality/non-equality comparisons,
but is not ok when it is used in other comparisons. 1-bit sign_extract has
range [-1,0] and
[-1,0] < -1 is always false.

  parent reply	other threads:[~2024-05-15 10:02 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 [this message]
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
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-JIe8AOhkIx@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: link
Be 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).