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] VR-VALUES: Rename op0/op1 to op1/op2 for test_for_singularity
Date: Mon, 4 Sep 2023 23:56:21 -0600	[thread overview]
Message-ID: <2f767166-9971-4b55-8cd5-d1b79480ac25@gmail.com> (raw)
In-Reply-To: <20230901173059.791894-1-apinski@marvell.com>



On 9/1/23 11:30, Andrew Pinski via Gcc-patches wrote:
> As requested and make easier to understand with the new ranger
> code, rename the arguments op0/op1 to op1/op2.
> 
> OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions
> 
> gcc/ChangeLog:
> 
> 	* vr-values.cc (test_for_singularity): Rename
> 	arguments op0/op1 to op1/op2.
OK
jeff

      parent reply	other threads:[~2023-09-05  5:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 17:30 Andrew Pinski
2023-09-01 17:30 ` [PATCH 2/2] VR-VALUES: Rewrite test_for_singularity using range_op_handler Andrew Pinski
2023-09-05  6:06   ` Jeff Law
2023-09-05  7:12     ` Andrew Pinski
2023-09-29 20:17       ` Jeff Law
2023-09-05  5:56 ` Jeff Law [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=2f767166-9971-4b55-8cd5-d1b79480ac25@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).