From: Lulu Cheng <chenglulu@loongson.cn>
To: WANG Xuerui <i@xen0n.name>,
gcc-patches@gcc.gnu.org, mliska@suse.cz, dmalcolm@redhat.com
Cc: xry111@xry111.site, xuchenghua@loongson.cn
Subject: Re: [PATCH] Libvtv-test: Fix the problem that scansarif.exp cannot be found in libvtv regression test.
Date: Tue, 27 Sep 2022 11:44:24 +0800 [thread overview]
Message-ID: <f5133fcc-c7ac-319c-92f0-77a0f84490a7@loongson.cn> (raw)
In-Reply-To: <7861c25d-3397-43d9-f29a-7a3252dd5d49@xen0n.name>
Sorry, I will try to avoid this problem in the future.
在 2022/9/27 上午11:30, WANG Xuerui 写道:
>
> On 2022/9/27 11:16, Lulu Cheng wrote:
>> r13-967 add ARRIF output format. However libvtv does not add
>> support.
>
> "SARIF support was added in r13-967 but libvtv wasn't updated."
>
> (Tip: always remember that English, unlike Chinese, isn't a
> "topic-prominent" language, meaning you should almost never put the
> "topic" at subject position of the sentence. IOW, if you find your
> English to be a perfect 1:1 mapping to some Chinese sentence, which is
> the case here, it's highly likely you need to improve it somehow. This
> is by no means personal, but the same pattern of broken English has
> been appearing in your and your teammates' commits since forever, so
> I'm afraid I have to point out.)
>
>>
>> commit 6cf276ddf22066af780335cd0072d2c27aabe468
>> Author: David Malcolm <dmalcolm@redhat.com>
>> Date: Thu Jun 2 15:40:22 2022 -0400
>>
>> diagnostics: add SARIF output format
>
> And I don't think this reference is necessary, r13-967 is already a
> precise description.
>
>>
>> libvtv/ChangeLog:
>>
>> * testsuite/lib/libvtv-dg.exp: Add load_gcc_lib of scansarif.exp.
> "Load scansarif.exp." -- another example of redundant expression (no
> pun intended on "expression").
>> ---
>> libvtv/testsuite/lib/libvtv-dg.exp | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/libvtv/testsuite/lib/libvtv-dg.exp
>> b/libvtv/testsuite/lib/libvtv-dg.exp
>> index b140c194cdc..454d916e556 100644
>> --- a/libvtv/testsuite/lib/libvtv-dg.exp
>> +++ b/libvtv/testsuite/lib/libvtv-dg.exp
>> @@ -12,6 +12,8 @@
>> # along with this program; if not, write to the Free Software
>> # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
>> 02110-1301, USA.
>> +load_gcc_lib scansarif.exp
>> +
>> proc libvtv-dg-test { prog do_what extra_tool_flags } {
>> return [gcc-dg-test-1 libvtv_target_compile $prog $do_what
>> $extra_tool_flags]
>> }
> Otherwise LGTM.
prev parent reply other threads:[~2022-09-27 3:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 3:16 Lulu Cheng
2022-09-27 3:30 ` WANG Xuerui
2022-09-27 3:44 ` Lulu Cheng [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=f5133fcc-c7ac-319c-92f0-77a0f84490a7@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=mliska@suse.cz \
--cc=xry111@xry111.site \
--cc=xuchenghua@loongson.cn \
/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).