From: chenglulu <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>,
Richard Biener <richard.guenther@gmail.com>
Cc: chenxiaolong <chenxiaolong@loongson.cn>,
YunQiang Su <wzssyqa@gmail.com>,
gcc-patches@gcc.gnu.org, i@xen0n.name, xuchenghua@loongson.cn,
schwab@linux-m68k.org, ci_notify@linaro.org
Subject: Re: [PATCH v2] LoongArch: testsuite:Added additional vectorization "-mlsx" option.
Date: Thu, 18 Jan 2024 16:49:53 +0800 [thread overview]
Message-ID: <cb657644-94c5-6c94-713c-a2bab402acca@loongson.cn> (raw)
In-Reply-To: <49d8b75b829f8a1cf1da72c6f38bc63a78b861ee.camel@xry111.site>
在 2024/1/18 下午3:44, Xi Ruoyao 写道:
> On Thu, 2024-01-18 at 15:15 +0800, chenglulu wrote:
>
>>> gcc.dg/tree-ssa/scev-16.c is OK to move
>>> gcc.dg/pr104992.c should simply add -fno-tree-vectorize to the used
>>> options and remove the vect_* stuff
>> Hi Richard:
>>
>> I have a question. I don't understand the purpose of adding
>> '-fno-tree-vectorize' here.
> I don't think -fno-tree-vectorize will make a difference here. This
> test case uses __attribute__((vector_size(...))) explicitly so the
> vector operation will be used even if -fno-tree-vectorize.
>
Yes, I did the test and compared the intermediate results and saw no
difference.
“remove the vect_* stuff”，I don’t quite understand what it means either.:-(
next prev parent reply other threads:[~2024-01-18 8:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 7:28 chenxiaolong
2024-01-13 13:13 ` Xi Ruoyao
2024-01-15 1:29 ` chenxiaolong
2024-01-15 4:10 ` Xi Ruoyao
2024-01-15 6:32 ` YunQiang Su
2024-01-15 6:42 ` Xi Ruoyao
2024-01-15 7:10 ` chenxiaolong
2024-01-15 7:50 ` Xi Ruoyao
2024-01-16 2:57 ` chenxiaolong
2024-01-16 4:58 ` Xi Ruoyao
2024-01-16 9:51 ` Xi Ruoyao
2024-01-16 10:20 ` Richard Biener
2024-01-18 7:15 ` chenglulu
2024-01-18 7:44 ` Xi Ruoyao
2024-01-18 8:49 ` chenglulu [this message]
2024-01-18 14:12 ` chenglulu
2024-01-15 7:26 ` chenglulu
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=cb657644-94c5-6c94-713c-a2bab402acca@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=chenxiaolong@loongson.cn \
--cc=ci_notify@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=richard.guenther@gmail.com \
--cc=schwab@linux-m68k.org \
--cc=wzssyqa@gmail.com \
--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).