public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112276] [14 Regression] wrong code with -O2 -msse4.2 since r14-4964-g7eed861e8ca3f5
Date: Mon, 30 Oct 2023 05:54:25 +0000 [thread overview]
Message-ID: <bug-112276-4-mLSlCfFL2o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112276-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112276
--- Comment #5 from Zdenek Sojka <zsojka at seznam dot cz> ---
(In reply to Hongtao.liu from comment #4)
> -(define_split
> - [(set (match_operand:V2HI 0 "register_operand")
> - (eq:V2HI
> - (eq:V2HI
> - (us_minus:V2HI
> - (match_operand:V2HI 1 "register_operand")
> - (match_operand:V2HI 2 "register_operand"))
> - (match_operand:V2HI 3 "const0_operand"))
> - (match_operand:V2HI 4 "const0_operand")))]
> - "TARGET_SSE4_1"
> - [(set (match_dup 0)
> - (umin:V2HI (match_dup 1) (match_dup 2)))
> - (set (match_dup 0)
> - (eq:V2HI (match_dup 0) (match_dup 2)))])
>
> the splitter is wrong when op1 == op2.(the original pattern returns 0, after
> splitter, it returns 1)
> So remove the splitter.
Thank you for having a look. I have other testcases, possibly related, that are
being reduced now, failing at -O2 only; so -msse4.2 might not be the only
broken target. I will open a new PR if those will still be broken after this is
fixed; alternatively, I can upload the testcases here, once they are reduced.
next prev parent reply other threads:[~2023-10-30 5:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 15:18 [Bug target/112276] New: [14 Regression] wrong code with -O2 -msse4.2 zsojka at seznam dot cz
2023-10-29 16:06 ` [Bug target/112276] " pinskia at gcc dot gnu.org
2023-10-29 16:13 ` pinskia at gcc dot gnu.org
2023-10-29 20:05 ` [Bug target/112276] [14 Regression] wrong code with -O2 -msse4.2 since r14-4964-g7eed861e8ca3f5 tkoenig at gcc dot gnu.org
2023-10-30 2:49 ` crazylht at gmail dot com
2023-10-30 5:49 ` crazylht at gmail dot com
2023-10-30 5:54 ` zsojka at seznam dot cz [this message]
2023-10-30 18:46 ` zsojka at seznam dot cz
2023-10-31 3:25 ` cvs-commit at gcc dot gnu.org
2023-10-31 3:25 ` crazylht at gmail dot com
2023-11-14 14:06 ` rguenth 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-112276-4-mLSlCfFL2o@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).