From: Xi Ruoyao <xry111@mengyan1223.wang>
To: xuchenghua@loongson.cn, gcc-patches@gcc.gnu.org
Cc: chenglulu@loongson.cn, joseph@codesourcery.com
Subject: Re: [PATCH v7 11/12] LoongArch Port: gcc/testsuite
Date: Fri, 25 Feb 2022 03:32:04 +0800 [thread overview]
Message-ID: <116a44c84b7986d4b3f2808242e38c2a34a3b2a2.camel@mengyan1223.wang> (raw)
In-Reply-To: <20220212031142.1165933-12-xuchenghua@loongson.cn>
On Sat, 2022-02-12 at 11:11 +0800, xuchenghua@loongson.cn wrote:
> From: chenglulu <chenglulu@loongson.cn>
>
> 2022-02-12 Chenghua Xu <xuchenghua@loongson.cn>
> Lulu Cheng <chenglulu@loongson.cn>
>
> gcc/testsuite/
spec-barrier tests fail with:
./testsuite/c-c++-common/spec-barrier-1.c:21:3: warning: this target
does not define a speculation barrier; your program will still execute
correctly, but incorrect speculation may not be restricted
I'd seen some news saying your uarch has in-silicon defense for
speculation related vulnerabilities. If this is true you can just make
__builtin_speculation_safe_value a nop. Quote from gcc internal doc:
> If this pattern is not defined then the default expansion of
> '__builtin_speculation_safe_value' will emit a warning. You can
> suppress this warning by defining this pattern with a final
> condition of '0' (zero), which tells the compiler that a
> speculation barrier is not needed for this target.
--
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-02-24 19:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 3:11 [PATCH v7 00/12] Add LoongArch support xuchenghua
2022-02-12 3:11 ` [PATCH v7 01/12] LoongArch Port: Regenerate configure xuchenghua
2022-02-12 3:11 ` [PATCH v7 02/12] LoongArch Port: gcc build xuchenghua
2022-02-24 19:17 ` Xi Ruoyao
2022-02-12 3:11 ` [PATCH v7 03/12] LoongArch Port: Regenerate gcc/configure xuchenghua
2022-02-12 3:11 ` [PATCH v7 04/12] LoongArch Port: Machine description files xuchenghua
2022-02-12 3:11 ` [PATCH v7 05/12] LoongArch Port: Machine description C files and .h files xuchenghua
2022-02-24 19:37 ` Xi Ruoyao
2022-02-12 3:11 ` [PATCH v7 06/12] LoongArch Port: Builtin functions xuchenghua
2022-02-12 3:11 ` [PATCH v7 07/12] LoongArch Port: Builtin macros xuchenghua
2022-02-12 3:11 ` [PATCH v7 08/12] LoongArch Port: libgcc xuchenghua
2022-02-24 17:42 ` Xi Ruoyao
2022-02-12 3:11 ` [PATCH v7 09/12] LoongArch Port: Regenerate libgcc/configure xuchenghua
2022-02-12 3:11 ` [PATCH v7 10/12] LoongArch Port: libgomp xuchenghua
2022-02-12 3:11 ` [PATCH v7 11/12] LoongArch Port: gcc/testsuite xuchenghua
2022-02-24 19:32 ` Xi Ruoyao [this message]
2022-02-28 2:55 ` 程璐璐
2022-02-12 3:11 ` [PATCH v7 12/12] LoongArch Port: Add doc xuchenghua
2022-02-20 6:10 ` Ping ?: [PATCH v7 00/12] Add LoongArch support Paul Hua
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=116a44c84b7986d4b3f2808242e38c2a34a3b2a2.camel@mengyan1223.wang \
--to=xry111@mengyan1223.wang \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--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).