From: Jeff Law <jeffreyalaw@gmail.com>
To: Tamar Christina <Tamar.Christina@arm.com>,
Richard Biener <richard.guenther@gmail.com>,
Andrew Pinski <pinskia@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
nd <nd@arm.com>, "rguenther@suse.de" <rguenther@suse.de>
Subject: Re: [PATCH 1/2]middle-end Fold BIT_FIELD_REF and Shifts into BIT_FIELD_REFs alone
Date: Mon, 31 Oct 2022 10:24:16 -0600 [thread overview]
Message-ID: <60cf08d0-1139-05dd-eb0c-358005fe5d70@gmail.com> (raw)
In-Reply-To: <VI1PR08MB5325510F8C42F1B0C43D5E06FF379@VI1PR08MB5325.eurprd08.prod.outlook.com>
On 10/31/22 05:51, Tamar Christina via Gcc-patches wrote:
> Hi All,
>
> Here's a respin addressing review comments.
>
> Bootstrapped Regtested on aarch64-none-linux-gnu, x86_64-pc-linux-gnu
> and no issues.
>
> Ok for master?
>
> Thanks,
> Tamar
>
> gcc/ChangeLog:
>
> * match.pd: Add bitfield and shift folding.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/bitshift_1.c: New.
> * gcc.dg/bitshift_2.c: New.
OK
jeff
next prev parent reply other threads:[~2022-10-31 16:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 11:42 Tamar Christina
2022-09-23 11:43 ` [PATCH 2/2]AArch64 Perform more late folding of reg moves and shifts which arrive after expand Tamar Christina
2022-09-23 14:32 ` Richard Sandiford
2022-10-31 11:48 ` Tamar Christina
2022-11-14 21:54 ` Richard Sandiford
2022-11-14 21:59 ` Richard Sandiford
2022-12-01 16:25 ` Tamar Christina
2022-12-01 18:38 ` Richard Sandiford
2022-09-24 18:38 ` [PATCH 1/2]middle-end Fold BIT_FIELD_REF and Shifts into BIT_FIELD_REFs alone Jeff Law
2022-09-28 13:19 ` Tamar Christina
2022-09-28 17:25 ` Jeff Law
2022-09-24 18:57 ` Andrew Pinski
2022-09-26 4:55 ` Tamar Christina
2022-09-26 8:05 ` Richard Biener
2022-09-26 15:24 ` Andrew Pinski
2022-09-27 12:40 ` Richard Biener
2022-10-31 11:51 ` Tamar Christina
2022-10-31 16:24 ` Jeff Law [this message]
2022-11-07 13:29 ` Richard Biener
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=60cf08d0-1139-05dd-eb0c-358005fe5d70@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=Tamar.Christina@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--cc=pinskia@gmail.com \
--cc=rguenther@suse.de \
--cc=richard.guenther@gmail.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).