From: "Xin Liu" <xin.liu@oss.cipunited.com>
To: "Jeff Law" <jeffreyalaw@gmail.com>, <gcc-patches@gcc.gnu.org>
Cc: "Matthew Fortune" <matthew.fortune@imgtec.com>
Subject: Re: [PATCH] Testsuite: Disable micromips for MSA tests
Date: Tue, 14 Mar 2023 13:46:49 +0800 [thread overview]
Message-ID: <54e9b34f-06e3-f184-96d5-52b137d1433c@oss.cipunited.com> (raw)
In-Reply-To: <444a2cf7-c3a9-255e-63eb-12ccd8f06df0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
Thanks for your feedback. You're right that MicroMIPS doesn't support
MSA, so disabling micromips for MSA tests is a reasonable change.
I'll make sure to include a ChangeLog entry with a clear description of
future patches. Thanks for the suggestions, and I'll strive to improve
my work based on your feedback.
On 2023/3/11 23:42, Jeff Law wrote:
>
>
> On 2/20/23 19:39, Xin Liu wrote:
>> From: Matthew Fortune <matthew.fortune@imgtec.com>
>>
>> ---
>> gcc/testsuite/gcc.target/mips/mips.exp | 1 +
>> 1 file changed, 1 insertion(+)
> Unfortunately, you haven't given anyone any background that would
> allow them to evaluate/review this patch.
>
> I'm guessing that MSA does not support micromips, is that correct?
>
> And for the future, please include a ChangeLog entry with patches. A
> ChangeLog entry describes what changed, not why something changes. A
> reasonable ChangeLog for this patch might be:
>
> gcc/testsuite:
> * gcc.target/mips/mips.exp (mips-dg-options): Disable micromips
> for MSA tests.
>
> Jeff
next prev parent reply other threads:[~2023-03-14 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 2:39 Xin Liu
2023-03-11 15:42 ` Jeff Law
2023-03-14 5:46 ` Xin Liu [this message]
2023-03-19 17:31 ` 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=54e9b34f-06e3-f184-96d5-52b137d1433c@oss.cipunited.com \
--to=xin.liu@oss.cipunited.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=matthew.fortune@imgtec.com \
/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).