From: Palmer Dabbelt <palmer@dabbelt.com>
To: gcc-patches@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, apinski@marvell.com
Subject: Re: [PATCH 00/10] [RISCV] Fix/improve the RISCV backend
Date: Mon, 22 Aug 2022 13:44:22 -0700 (PDT) [thread overview]
Message-ID: <mhng-d68a73df-dcec-4839-a212-f2b70fd08e17@palmer-mbp2014> (raw)
In-Reply-To: <1660860233-11175-1-git-send-email-apinski@marvell.com>
On Thu, 18 Aug 2022 15:03:43 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
> From: Andrew Pinski <apinski@marvell.com>
>
> This set of patches fixes a few RISCV issues and does a few
> cleanups. Including moving all of the iterators to iterators.md like
> many newer backends.
> It also fixes a few PRs which I filed including the RISCV32 issue
> with ZBS enabled.
>
> Thanks,
> Andrew Pinski
>
> Andrew Pinski (10):
> [RISCV] Move iterators from riscv.md to iterators.md
> [RISCV] Move iterators from bitmanip.md to iterators.md
> [RISCV] Move iterators from sync.md to iterators.md
> [RISCV] Add the list of operand modifiers to riscv.md too
> [RISCV] Add %~ to print w if TARGET_64BIT and use it
> [RISCV] Use constraints/predicates instead of checking const_int
> directly for shNadd patterns
> [RISCV] Use a constraint for bset<mode>_mask and bset<mode>_1_mask
> [RISCV] Fix PR 106586: riscv32 vs ZBS
> [RISCV] Add constraints for
> not_single_bit_mask_operand/single_bit_mask_operand
> [RISCV] Fix PR 106632 and PR 106588 a few constraints in bitmanip.md
>
> gcc/config/riscv/bitmanip.md | 56 ++------
> gcc/config/riscv/constraints.md | 28 ++++
> gcc/config/riscv/iterators.md | 245 ++++++++++++++++++++++++++++++++
> gcc/config/riscv/predicates.md | 9 +-
> gcc/config/riscv/riscv.cc | 35 ++++-
> gcc/config/riscv/riscv.h | 4 +-
> gcc/config/riscv/riscv.md | 199 +++-----------------------
> gcc/config/riscv/sync.md | 4 -
> 8 files changed, 352 insertions(+), 228 deletions(-)
> create mode 100644 gcc/config/riscv/iterators.md
Aside from the minor issue I pointed out in my reply to 10, these all
look good to me. Thanks!
prev parent reply other threads:[~2022-08-22 20:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 22:03 apinski
2022-08-18 22:03 ` [PATCH 01/10] [RISCV] Move iterators from riscv.md to iterators.md apinski
2022-08-18 22:03 ` [PATCH 02/10] [RISCV] Move iterators from bitmanip.md " apinski
2022-08-18 22:03 ` [PATCH 03/10] [RISCV] Move iterators from sync.md " apinski
2022-08-18 22:03 ` [PATCH 04/10] [RISCV] Add the list of operand modifiers to riscv.md too apinski
2022-08-18 22:03 ` [PATCH 05/10] [RISCV] Add %~ to print w if TARGET_64BIT and use it apinski
2022-08-18 22:03 ` [PATCH 06/10] [RISCV] Use constraints/predicates instead of checking const_int directly for shNadd patterns apinski
2022-08-22 8:47 ` Kito Cheng
2022-08-18 22:03 ` [PATCH 07/10] [RISCV] Use a constraint for bset<mode>_mask and bset<mode>_1_mask apinski
2022-08-18 22:03 ` [PATCH 08/10] [RISCV] Fix PR 106586: riscv32 vs ZBS apinski
2022-08-18 22:03 ` [PATCH 09/10] [RISCV] Add constraints for not_single_bit_mask_operand/single_bit_mask_operand apinski
2022-08-18 22:03 ` [PATCH 10/10] [RISCV] Fix PR 106632 and PR 106588 a few constraints in bitmanip.md apinski
2022-08-22 9:09 ` Kito Cheng
2022-08-22 20:44 ` Palmer Dabbelt
2022-08-22 20:44 ` Palmer Dabbelt [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=mhng-d68a73df-dcec-4839-a212-f2b70fd08e17@palmer-mbp2014 \
--to=palmer@dabbelt.com \
--cc=apinski@marvell.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).