public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107269] wrong code at -O1 and above with "-fno-tree-ccp" on x86_64-linux-gnu
Date: Mon, 17 Oct 2022 03:26:55 +0000 [thread overview]
Message-ID: <bug-107269-4-HhlxOYcDgU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107269-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107269
Hongtao.liu <crazylht at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |crazylht at gmail dot com
--- Comment #3 from Hongtao.liu <crazylht at gmail dot com> ---
Looks like the same issue as PR107172 since below change can also pass all the
testcase in the PR.
diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md
index 8e847520491..be815341af5 100644
--- a/gcc/config/i386/i386.md
+++ b/gcc/config/i386/i386.md
@@ -21335,7 +21335,7 @@ (define_insn "*x86_mov<mode>cc_0_m1_neg"
(define_expand "x86_mov<mode>cc_0_m1_neg"
[(parallel
[(set (match_operand:SWI48 0 "register_operand")
- (neg:SWI48 (ltu:SWI48 (reg:CCC FLAGS_REG) (const_int 0))))
+ (neg:SWI48 (ltu:SWI48 (reg:CC FLAGS_REG) (const_int 0))))
(clobber (reg:CC FLAGS_REG))])])
(define_split
next prev parent reply other threads:[~2022-10-17 3:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 18:22 [Bug tree-optimization/107269] New: " zhendong.su at inf dot ethz.ch
2022-10-14 18:29 ` [Bug tree-optimization/107269] " zhendong.su at inf dot ethz.ch
2022-10-15 20:45 ` zhendong.su at inf dot ethz.ch
2022-10-17 3:26 ` crazylht at gmail dot com [this message]
2022-10-17 7:48 ` rguenth at gcc dot gnu.org
2022-10-17 19:07 ` hjl.tools at gmail dot com
2022-10-18 3:31 ` crazylht at gmail dot com
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-107269-4-HhlxOYcDgU@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).