From: Richard Biener <rguenther@suse.de>
To: Jiufu Guo <guojiufu@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org, jeffreyalaw@gmail.com,
richard.sandiford@arm.com, segher@kernel.crashing.org,
dje.gcc@gmail.com, linkw@gcc.gnu.org, bergner@linux.ibm.com,
amacleod@redhat.com, aldyh@redhat.com
Subject: Re: [PATCH 2/2] testcase: rename pr111303.c to pr111324.c
Date: Tue, 19 Sep 2023 12:51:12 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2309191251070.5561@jbgna.fhfr.qr> (raw)
In-Reply-To: <20230919052353.3208707-2-guojiufu@linux.ibm.com>
On Tue, 19 Sep 2023, Jiufu Guo wrote:
> Hi,
>
> When commit the fix for pr111324, the test cases was named as pr111303.c
> by mistake. Here, rename it to pr111324.c
>
> Is this ok for trunk?
OK.
> BR,
> Jeff (Jiufu Guo)
>
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/tree-ssa/pr111303.c: Rename to ...
> * gcc.dg/tree-ssa/pr111324.c: ... this.
> ---
> gcc/testsuite/gcc.dg/tree-ssa/{pr111303.c => pr111324.c} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename gcc/testsuite/gcc.dg/tree-ssa/{pr111303.c => pr111324.c} (100%)
>
> diff --git a/gcc/testsuite/gcc.dg/tree-ssa/pr111303.c b/gcc/testsuite/gcc.dg/tree-ssa/pr111324.c
> similarity index 100%
> rename from gcc/testsuite/gcc.dg/tree-ssa/pr111303.c
> rename to gcc/testsuite/gcc.dg/tree-ssa/pr111324.c
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH,
Frankenstrasse 146, 90461 Nuernberg, Germany;
GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)
next prev parent reply other threads:[~2023-09-19 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 5:23 [PATCH 1/2] using overflow_free_p to simplify pattern Jiufu Guo
2023-09-19 5:23 ` [PATCH 2/2] testcase: rename pr111303.c to pr111324.c Jiufu Guo
2023-09-19 12:51 ` Richard Biener [this message]
2023-09-19 12:50 ` [PATCH 1/2] using overflow_free_p to simplify pattern Richard Biener
2023-09-21 5:22 ` Jiufu Guo
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=nycvar.YFH.7.77.849.2309191251070.5561@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=jeffreyalaw@gmail.com \
--cc=linkw@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
--cc=segher@kernel.crashing.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).