public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104610] memcmp () == 0 can be optimized better for avx512f
Date: Sat, 26 Feb 2022 20:26:05 +0000 [thread overview]
Message-ID: <bug-104610-4-P8pnBgDfOc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104610-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104610
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |104704
--- Comment #12 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Hongtao.liu from comment #8)
> Created attachment 52495 [details]
> untested patch.
>
> With the patch, it exposes one potential issue related to dse(or
> ix86_gen_scratch_sse_rtx usage). in dse1, it try to replace load insn with
> equivalent value, but the inserted new insns(insn 45, insn 44, insn 46) will
> set xmm31, but dse is not aware of that, and xmm31 is alive and will be used
> by insn 10 which is exactly after new added insns, and it breaks data flow.
>
I opened PR 104704.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104704
[Bug 104704] [12 Regression] ix86_gen_scratch_sse_rtx doesn't work with
explicit XMM7/XMM15/XMM31 usage
next prev parent reply other threads:[~2022-02-26 20:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 11:00 [Bug target/104610] New: " pinskia at gcc dot gnu.org
2022-02-21 11:01 ` [Bug target/104610] " pinskia at gcc dot gnu.org
2022-02-22 4:03 ` crazylht at gmail dot com
2022-02-22 5:54 ` crazylht at gmail dot com
2022-02-22 5:55 ` crazylht at gmail dot com
2022-02-22 6:18 ` crazylht at gmail dot com
2022-02-22 6:32 ` crazylht at gmail dot com
2022-02-23 2:15 ` crazylht at gmail dot com
2022-02-23 6:18 ` crazylht at gmail dot com
2022-02-23 21:04 ` hjl.tools at gmail dot com
2022-02-24 5:33 ` crazylht at gmail dot com
2022-02-24 6:00 ` hjl.tools at gmail dot com
2022-02-26 20:26 ` hjl.tools at gmail dot com [this message]
2022-02-27 19:02 ` hjl.tools at gmail dot com
2022-02-27 19:29 ` hjl.tools at gmail dot com
2022-03-04 3:03 ` hjl.tools at gmail dot com
2022-03-28 5:05 ` crazylht at gmail dot com
2022-03-28 5:27 ` crazylht at gmail dot com
2022-05-18 2:47 ` cvs-commit at gcc dot gnu.org
2022-05-18 2:49 ` crazylht at gmail dot com
2022-06-16 7:41 ` crazylht at gmail dot com
2023-06-28 10:12 ` cvs-commit at gcc dot gnu.org
2023-06-28 11:05 ` ubizjak at gmail dot com
2023-10-10 7:37 ` crazylht at gmail dot com
2023-10-30 3:10 ` 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-104610-4-P8pnBgDfOc@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).