From: chenglulu <chenglulu@loongson.cn>
To: chenxiaolong <chenxiaolong@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: xry111@xry111.site, i@xen0n.name, xuchenghua@loongson.cn,
schwab@linux-m68k.org
Subject: Re:[pushed] [PATCH v1] LoongArch: testsuite:Fixed a bug that added a target check error.
Date: Wed, 10 Jan 2024 20:18:32 +0800 [thread overview]
Message-ID: <68a7e77a-2ba8-11fe-0c7d-c64fdfd420ad@loongson.cn> (raw)
In-Reply-To: <20240110072459.8851-1-chenxiaolong@loongson.cn>
Pushed to r14-7096.
在 2024/1/10 下午3:24, chenxiaolong 写道:
> After the code is committed in r14-6948, GCC regression testing on some
> architectures will produce the following error:
>
> "error executing dg-final: unknown effective target keyword `loongarch*-*-*'"
>
> gcc/testsuite/ChangeLog:
>
> * lib/target-supports.exp: Removed an issue with "target keyword"
> checking errors on LoongArch architecture.
> ---
> gcc/testsuite/lib/target-supports.exp | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
> index 5c6bb602cc0..dbc4f016091 100644
> --- a/gcc/testsuite/lib/target-supports.exp
> +++ b/gcc/testsuite/lib/target-supports.exp
> @@ -7994,7 +7994,6 @@ proc check_effective_target_vect_widen_mult_qi_to_hi { } {
> || ([istarget aarch64*-*-*]
> && ![check_effective_target_aarch64_sve])
> || [is-effective-target arm_neon]
> - || [is-effective-target loongarch*-*-*]
> || ([istarget s390*-*-*]
> && [check_effective_target_s390_vx]))
> || [istarget amdgcn-*-*] }}]
> @@ -8019,7 +8018,6 @@ proc check_effective_target_vect_widen_mult_hi_to_si { } {
> && ![check_effective_target_aarch64_sve])
> || [istarget i?86-*-*] || [istarget x86_64-*-*]
> || [is-effective-target arm_neon]
> - || [is-effective-target loongarch*-*-*]
> || ([istarget s390*-*-*]
> && [check_effective_target_s390_vx]))
> || [istarget amdgcn-*-*] }}]
prev parent reply other threads:[~2024-01-10 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 7:24 chenxiaolong
2024-01-10 12:18 ` chenglulu [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=68a7e77a-2ba8-11fe-0c7d-c64fdfd420ad@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=chenxiaolong@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=schwab@linux-m68k.org \
--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).