From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RISC-V: Revive test case PR 102957
Date: Tue, 29 Aug 2023 11:12:20 +0900 [thread overview]
Message-ID: <3f48dab9-0d40-4c75-8b06-298e54a45740@irq.a4lg.com> (raw)
In-Reply-To: <8213c477-1339-c15a-5ae2-d4a920f38f20@gmail.com>
On 2023/08/29 7:01, Jeff Law wrote:
>
>
> On 8/11/23 08:29, Tsukasa OI wrote:
>> On 2023/08/11 23:15, Jeff Law wrote:
>
>>>
>>
>> Originally, it tested that a two letter extension ('Zb') is accepted by
>> GCC (because the background of PR 102957 was GCC assumed multi-letter
>> 'Z' extensions are three letters or more).
>>
>> After rejecting unrecognized extensions, "dg-error" is added **just to
>> avoid the test failure** and that doesn't look right. Yes, we now don't
>> have an ICE (like in the original report) but after the PR 102957 fix,
>> we just accepted it, not rejecting it.
>>
>> Instead, we have a valid (recognized) two-letter 'Z' extension: 'Zk'. I
>> think replacing "zb" with "zk" is more correct considering the original
>> bug report (PR 102957) and its assumption.
>>
>> cf. <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102957>
> Thanks. It still seems to me we want to have two tests here.
>
> I would suggest leaving pr102957.c alone since that tests that we give a
> proper error for "zb". Then create a new test that verifies "zk" is
> accepted without error.
>
> jeff
>
Okay, that's a great compromise.
I will make v2 to add pr102957-2.c (like so) to reflect my intention and
keep the original pr102957.c.
Thanks,
Tsukasa
next prev parent reply other threads:[~2023-08-29 2:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 9:11 Tsukasa OI
2023-08-11 14:15 ` Jeff Law
2023-08-11 14:29 ` Tsukasa OI
2023-08-28 22:01 ` Jeff Law
2023-08-29 2:12 ` Tsukasa OI [this message]
2023-08-29 3:28 ` [PATCH v2] RISC-V: Make PR 102957 tests more comprehensive Tsukasa OI
2023-08-29 13:44 ` 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=3f48dab9-0d40-4c75-8b06-298e54a45740@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.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).