From: Xi Ruoyao <xry111@xry111.site>
To: Yujie Yang <yangyujie@loongson.cn>
Cc: gcc-patches@gcc.gnu.org, xuchenghua@loongson.cn,
panchenghui@loongson.cn, chenglulu@loongson.cn
Subject: Re: [PATCH v1 2/6] LoongArch: improved target configuration interface
Date: Mon, 14 Aug 2023 16:49:11 +0800 [thread overview]
Message-ID: <0733349c1d233eb845a26d9992a1f83b8a2e7a7a.camel@xry111.site> (raw)
In-Reply-To: <20230814084404.a62t2odnjzqhtofg@loongson-pc>
On Mon, 2023-08-14 at 16:44 +0800, Yujie Yang wrote:
> I assume we all want:
>
> (1) -mlasx -mlsx -> enable LSX and LASX
> (2) -mlasx -mno-lsx -> disable LSX and LASX
> (3) -mno-lsx -mlasx -> enable LSX and LASX
Yes.
> Unless we declare -mlsx / -mlasx as driver deferred, AFAIK there is no other way for
> us to know the actual order of appearnce of all -m[no-]l[a]sx options on the command
> line. All we know from GCC's option system would be a final on/off state of "lsx"
> and a final on/off state of "lasx".
But x86 does this correct;
$ echo __AVX__ + __AVX2__ | LANG= cpp -E -mno-avx -mavx2
# 0 "<stdin>"
# 0 "<built-in>"
# 0 "<command-line>"
# 1 "/usr/include/stdc-predef.h" 1 3 4
# 0 "<command-line>" 2
# 1 "<stdin>"
1 + 1
so there must be a way to handle this...
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-08-14 8:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 3:57 [PATCH v1 1/6] LoongArch: a symmetric multilib subdir layout Yang Yujie
2023-08-14 3:57 ` [PATCH v1 2/6] LoongArch: improved target configuration interface Yang Yujie
2023-08-14 5:22 ` Xi Ruoyao
2023-08-15 1:12 ` Yujie Yang
2023-08-14 5:29 ` Xi Ruoyao
2023-08-14 5:58 ` Xi Ruoyao
2023-08-14 6:01 ` Xi Ruoyao
2023-08-14 8:44 ` Yujie Yang
2023-08-14 8:49 ` Xi Ruoyao [this message]
2023-08-14 8:57 ` Yujie Yang
2023-08-14 8:58 ` Xi Ruoyao
2023-09-06 6:43 ` Richard Sandiford
2023-09-06 6:54 ` Yang Yujie
2023-08-14 3:57 ` [PATCH v1 3/6] LoongArch: define preprocessing macros "__loongarch_{arch,tune}" Yang Yujie
2023-08-14 5:24 ` Xi Ruoyao
2023-08-14 3:57 ` [PATCH v1 4/6] LoongArch: use -mstrict-align by default when building libraries Yang Yujie
2023-08-14 5:18 ` Xi Ruoyao
2023-08-14 3:57 ` [PATCH v1 5/6] LoongArch: export headers for building GCC plugins Yang Yujie
2023-08-14 3:57 ` [PATCH v1 6/6] LoongArch: support loongarch*-elf target Yang Yujie
2023-08-14 5:38 ` [PATCH v1 1/6] LoongArch: a symmetric multilib subdir layout Xi Ruoyao
2023-08-14 5:40 ` Xi Ruoyao
2023-08-14 7:37 ` Yujie Yang
2023-08-14 7:48 ` Xi Ruoyao
2023-08-14 10:18 ` Yujie Yang
2023-08-14 11:16 ` Xi Ruoyao
2023-08-15 1:29 ` Xi Ruoyao
2023-08-15 2:32 ` Yujie Yang
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=0733349c1d233eb845a26d9992a1f83b8a2e7a7a.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=panchenghui@loongson.cn \
--cc=xuchenghua@loongson.cn \
--cc=yangyujie@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).