From: Jeff Law <jeffreyalaw@gmail.com>
To: Andrew Pinski <apinski@marvell.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/2] Remove #if GIMPLE around 1 - a pattern
Date: Fri, 17 Feb 2023 15:12:05 -0700 [thread overview]
Message-ID: <78697ccd-f08c-fc55-7d45-9404951cfdea@gmail.com> (raw)
In-Reply-To: <20230217214538.2177094-2-apinski@marvell.com>
On 2/17/23 14:45, Andrew Pinski via Gcc-patches wrote:
> This removes the "#if GIMPLE" around the
> "1 - a" pattern as ssa_name_has_boolean_range
> (get_range_query) works when cfun is a nullptr.
>
> OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions.
>
> gcc/ChangeLog:
>
> * match.pd: Remove #if GIMPLE around the
> "1 - a" pattern
Both patches in this series are OK. They're really just a slight
refinement on a prior approved patch that addressed a regression.
jeff
next prev parent reply other threads:[~2023-02-17 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 21:45 [PATCH 1/2] Support get_range_query with a nullptr argument Andrew Pinski
2023-02-17 21:45 ` [PATCH 2/2] Remove #if GIMPLE around 1 - a pattern Andrew Pinski
2023-02-17 22:12 ` Jeff Law [this message]
2023-02-20 8:01 ` [PATCH 1/2] Support get_range_query with a nullptr argument 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=78697ccd-f08c-fc55-7d45-9404951cfdea@gmail.com \
--to=jeffreyalaw@gmail.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).