From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Kito Cheng <kito.cheng@gmail.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Vineet Gupta <vineetg@rivosinc.com>,
Jeff Law <jlaw@ventanamicro.com>,
Christoph Muellner <christoph.muellner@vrull.eu>
Subject: Re: [PATCH v2 0/2] Use Zbs with xori/ori/andi and polarity-reversed twobit-tests
Date: Fri, 18 Nov 2022 21:04:26 +0100 [thread overview]
Message-ID: <CAAeLtUCo7OmnNTTXphVxQDWn=-ih-7cD533W-iyKMbjxhV7StQ@mail.gmail.com> (raw)
In-Reply-To: <8ca4581a-cd38-5ba0-2bdc-158d58fdf52a@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2067 bytes --]
(Both) applied to master. Thanks!
--Philipp.
On Fri, 18 Nov 2022 at 20:13, Jeff Law <jeffreyalaw@gmail.com> wrote:
>
> On 11/18/22 04:09, Philipp Tomsich wrote:
> > We had a few patches on the list that shared predicates (for extending
> > the reach of xori and ori -- and for the branches on two
> > polarity-reversed bits) and thus depended on each other.
> >
> > These all had approval with requested changes, so these are now
> > collected together for v2.
> >
> > Note that this adds the (a & ~C) case, so please take a look on that
> > part and OK the updated series.
> >
> >
> >
> > Changes in v2:
> > - Collects already approved changes for v2 for (a | C) and (a ^ C).
> > - Pulls in the (already) approved branch on polarity-reversed bits
> > for v2, as it shares predicates with the other changes.
> > - Newly adds support for the (a & ~C) case.
> >
> > Philipp Tomsich (2):
> > RISC-V: Use bseti/bclri/binvi to extend reach of ori/andi/xori
> > RISC-V: Handle "(a & twobits) == singlebit" in branches using Zbs
> >
> > gcc/config/riscv/bitmanip.md | 79 +++++++++++++++++++
> > gcc/config/riscv/iterators.md | 8 ++
> > gcc/config/riscv/predicates.md | 33 ++++++++
> > gcc/config/riscv/riscv.h | 8 ++
> > .../riscv/{zbs-bclri.c => zbs-bclri-01.c} | 0
> > gcc/testsuite/gcc.target/riscv/zbs-bclri-02.c | 27 +++++++
> > gcc/testsuite/gcc.target/riscv/zbs-binvi.c | 22 ++++++
> > gcc/testsuite/gcc.target/riscv/zbs-bseti.c | 27 +++++++
> > .../gcc.target/riscv/zbs-if_then_else-01.c | 20 +++++
> > 9 files changed, 224 insertions(+)
> > rename gcc/testsuite/gcc.target/riscv/{zbs-bclri.c => zbs-bclri-01.c}
> (100%)
> > create mode 100644 gcc/testsuite/gcc.target/riscv/zbs-bclri-02.c
> > create mode 100644 gcc/testsuite/gcc.target/riscv/zbs-binvi.c
> > create mode 100644 gcc/testsuite/gcc.target/riscv/zbs-bseti.c
> > create mode 100644 gcc/testsuite/gcc.target/riscv/zbs-if_then_else-01.c
>
> 1/2 and 2/2 are both OK.
>
> jeff
>
>
prev parent reply other threads:[~2022-11-18 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 11:09 Philipp Tomsich
2022-11-18 11:10 ` [PATCH v2 1/2] RISC-V: Use bseti/bclri/binvi to extend reach of ori/andi/xori Philipp Tomsich
2022-11-18 11:10 ` [PATCH v2 2/2] RISC-V: Handle "(a & twobits) == singlebit" in branches using Zbs Philipp Tomsich
2022-11-18 19:13 ` [PATCH v2 0/2] Use Zbs with xori/ori/andi and polarity-reversed twobit-tests Jeff Law
2022-11-18 20:04 ` Philipp Tomsich [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='CAAeLtUCo7OmnNTTXphVxQDWn=-ih-7cD533W-iyKMbjxhV7StQ@mail.gmail.com' \
--to=philipp.tomsich@vrull.eu \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jlaw@ventanamicro.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.com \
--cc=vineetg@rivosinc.com \
/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).