From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] aarch64: Specify that FEAT_MOPS sequences clobber CC
Date: Tue, 6 Dec 2022 10:26:24 +0000 [thread overview]
Message-ID: <PAXPR08MB69265D53060C2CDDB4576AA5931B9@PAXPR08MB6926.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <PAXPR08MB6926BDABBC3C304C37B3E3AE93159@PAXPR08MB6926.eurprd08.prod.outlook.com>
> -----Original Message-----
> From: Kyrylo Tkachov
> Sent: Wednesday, November 30, 2022 5:40 PM
> To: gcc-patches@gcc.gnu.org
> Subject: [PATCH] aarch64: Specify that FEAT_MOPS sequences clobber CC
>
> Hi all,
>
> According to the architecture pseudocode the FEAT_MOPS sequences
> overwrite the NZCV flags
> as part of their operation, so GCC needs to model that in the relevant RTL
> patterns.
> For the testcase:
> void g();
> void foo (int a, size_t N, char *__restrict__ in,
> char *__restrict__ out)
> {
> if (a != 3)
> __builtin_memcpy (out, in, N);
> if (a > 3)
> g ();
> }
>
> we will currently generate:
> foo:
> cmp w0, 3
> bne .L6
> .L1:
> ret
> .L6:
> cpyfp [x3]!, [x2]!, x1!
> cpyfm [x3]!, [x2]!, x1!
> cpyfe [x3]!, [x2]!, x1!
> ble .L1 // Flags reused after CPYF* sequence
> b g
>
> This is wrong as the result of cmp needs to be recalculated after the MOPS
> sequence.
> With this patch we'll insert a "cmp w0, 3" before the ble, like what clang
> does.
>
> Bootstrapped and tested on aarch64-none-linux-gnu.
> Pushing to trunk and to the GCC 12 branch after some baking time.
Pushed to releases/gcc-12 now.
Thanks,
Kyrill
>
> Thanks,
> Kyrill
>
> gcc/ChangeLog:
>
> * config/aarch64/aarch64.md (aarch64_cpymemdi): Specify clobber
> of CC reg.
> (*aarch64_cpymemdi): Likewise.
> (aarch64_movmemdi): Likewise.
> (aarch64_setmemdi): Likewise.
> (*aarch64_setmemdi): Likewise.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/aarch64/mops_5.c: New test.
> * gcc.target/aarch64/mops_6.c: Likewise.
> * gcc.target/aarch64/mops_7.c: Likewise.
prev parent reply other threads:[~2022-12-06 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 17:40 Kyrylo Tkachov
2022-12-06 10:26 ` Kyrylo Tkachov [this message]
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=PAXPR08MB69265D53060C2CDDB4576AA5931B9@PAXPR08MB6926.eurprd08.prod.outlook.com \
--to=kyrylo.tkachov@arm.com \
--cc=gcc-patches@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).