From: Paul Hua <paul.hua.gm@gmail.com>
To: Matthew Fortune <Matthew.Fortune@imgtec.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [testsuite]MIPS remove duplicate div-x test
Date: Mon, 05 Jun 2017 02:17:00 -0000 [thread overview]
Message-ID: <CAKjxQHkbs7g15zFxqK3rGb5dE_qY-GHyWpWg-P=htUNrvfsEOg@mail.gmail.com> (raw)
In-Reply-To: <6D39441BF12EF246A7ABCE6654B0235380CB0E46@hhmail02.hh.imgtec.org>
Commited as r248868.
Thanks.
Paul.
On Mon, Jun 5, 2017 at 4:41 AM, Matthew Fortune
<Matthew.Fortune@imgtec.com> wrote:
> Hi Paul,
>
> Paul Hua <paul.hua.gm@gmail.com> writes:
>> cc: Matthew.
>>
>> ping.
>
> Sorry a little slow on the reply.
>
>> On Thu, Jun 1, 2017 at 3:35 PM, Paul Hua <paul.hua.gm@gmail.com> wrote:
>> > Hi,
>> >
>> > There are duplicate testcase in gcc.target/mips dir.
>> >
>> > div-5.c same as div-9.c.
>> > div-6.c same as div-10.c.
>> > div-7.c same as div-11.c.
>> > div-8.c same as div-12.c.
>> >
>> > Is this deliberate?
>
> I see no evidence of this being deliberate and has been like this since
> the original commit.
>
>> > Otherwise, the attached patch fixing this.
>> >
>> >
>> > Paul.
>> >
>> > ***ChangeLog***
>> >
>> > 2017-06-01 Chenghua Xu <paul.hua.gm@gmail.com>
>> >
>> > Remove duplicate div-x testcase.
>
> These kind of comments don't tend to go in a changelog.
>
>> > * gcc.target/mips/div-9.c: Delete.
>
> You could say "Delete duplicate test" here if you want though.
>
>> > * gcc.target/mips/div-10.c: Ditto.
>> > * gcc.target/mips/div-11.c: Ditto.
>> > * gcc.target/mips/div-12.c: Ditto.
>
> Otherwise OK. I can't remember if you have write access let me know
> if you need it committing. Thanks for finding this.
>
> Matthew
next prev parent reply other threads:[~2017-06-05 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 7:35 Paul Hua
2017-06-03 2:29 ` Paul Hua
2017-06-04 20:41 ` Matthew Fortune
2017-06-05 2:17 ` Paul Hua [this message]
2017-06-10 14:19 ` Maciej W. Rozycki
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='CAKjxQHkbs7g15zFxqK3rGb5dE_qY-GHyWpWg-P=htUNrvfsEOg@mail.gmail.com' \
--to=paul.hua.gm@gmail.com \
--cc=Matthew.Fortune@imgtec.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).