public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Andrew Pinski <apinski@marvell.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2] PHIOPT: Allow moving of some builtin calls
Date: Sun, 30 Apr 2023 13:11:58 -0600	[thread overview]
Message-ID: <9d1afa76-d68e-fa5d-98a9-76d9cd5a1123@gmail.com> (raw)
In-Reply-To: <20230428170213.677572-2-apinski@marvell.com>



On 4/28/23 11:02, Andrew Pinski via Gcc-patches wrote:
> While moving working on moving
> cond_removal_in_builtin_zero_pattern to match, I noticed
> that functions were not allowed to move as we reject all
> non-assignments.
> This changes to allowing a few calls which are known not
> to throw/trap. Right now it is restricted to ones
> which cond_removal_in_builtin_zero_pattern handles but
> adding more is just adding it to the switch statement.
> 
> gcc/ChangeLog:
> 
> 	* tree-ssa-phiopt.cc (empty_bb_or_one_feeding_into_p):
> 	Allow some builtin/internal function calls which
> 	are known not to trap/throw.
> 	(phiopt_worker::match_simplify_replacement):
> 	Use name instead of getting the lhs again.
OK
jeff

  reply	other threads:[~2023-04-30 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 17:02 [PATCH 0/2] Porting of builtin_zero_pattern to match Andrew Pinski
2023-04-28 17:02 ` [PATCH 1/2] PHIOPT: Allow moving of some builtin calls Andrew Pinski
2023-04-30 19:11   ` Jeff Law [this message]
2023-04-28 17:02 ` [PATCH 2/2] MATCH: add some of what phiopt's builtin_zero_pattern did Andrew Pinski
2023-04-30 19:13   ` Jeff Law

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=9d1afa76-d68e-fa5d-98a9-76d9cd5a1123@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).