From: Chenghui Pan <panchenghui@loongson.cn>
To: gcc-patches@gcc.gnu.org
Cc: xry111@xry111.site, i@xen0n.name, chenglulu@loongson.cn,
xuchenghua@loongson.cn
Subject: Re: [PATCH v2 0/2] Update target-supports.exp for LoongArch SX/ASX.
Date: Tue, 26 Sep 2023 20:09:22 +0800 [thread overview]
Message-ID: <079fcca8a797f866f64f8f87a372143ce28e7dd2.camel@loongson.cn> (raw)
In-Reply-To: <20230926115636.1367818-1-panchenghui@loongson.cn>
Correction: vect.exp will be set to run when target is capable of
running LASX instructions, otherwise it will be compiled only.
On Tue, 2023-09-26 at 19:56 +0800, Chenghui Pan wrote:
> This is an update of:
> https://gcc.gnu.org/pipermail/gcc-patches/2023-September/630953.html
>
> This version of patch set contains code that enable vect.exp for
> LoongArch
> target when target environment is capable of running LASX
> instructions.
>
> After some attemptions, we still need
> "check_effective_target_loongarch_sx"
> in "proc check_effective_target_vect_int_mod {}" to choose correct
> dg-final
> directives for LoongArch, because DEFAULT_VECTCFLAGS cannot affect
> pr104992.c
> which is invoked by gcc.dg/dg.exp (not vect.exp).
>
> Chenghui Pan (2):
> Enable vect.exp for LoongArch.
> Add LoongArch in check_effective_target_vect_int_mod according to
> ISA
> capabilities.
>
> gcc/testsuite/lib/target-supports.exp | 49
> +++++++++++++++++++++++++++
> 1 file changed, 49 insertions(+)
>
prev parent reply other threads:[~2023-09-26 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 11:56 Chenghui Pan
2023-09-26 11:56 ` [PATCH v2 1/2] Enable vect.exp for LoongArch Chenghui Pan
2023-09-26 11:56 ` [PATCH v2 2/2] Add LoongArch in check_effective_target_vect_int_mod according to ISA capabilities Chenghui Pan
2023-09-26 12:09 ` Chenghui Pan [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=079fcca8a797f866f64f8f87a372143ce28e7dd2.camel@loongson.cn \
--to=panchenghui@loongson.cn \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--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).