public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Yang Yujie <yangyujie@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: 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 14:01:21 +0800	[thread overview]
Message-ID: <4c0e6470a94d01017d631f4255e0382840c7a2e8.camel@xry111.site> (raw)
In-Reply-To: <40af845af299fa6ff1f05bc9f2daeeb9a662a2ef.camel@xry111.site>

On Mon, 2023-08-14 at 13:58 +0800, Xi Ruoyao via Gcc-patches wrote:
> On Mon, 2023-08-14 at 11:57 +0800, Yang Yujie wrote:
> > * Support options for LoongArch SIMD extensions:
> >   new configure options --with-simd={none,lsx,lasx};
> >   new driver options -m[no]-l[a]sx / -msimd={none,lsx,lasx}.
> 
> I suggest to rename --with-simd= to --with-ext= and accept a comma-
> separated ISA extension list, because we have non-SIMD ISA extensions.
> For example, "--with-ext=lasx,lbt" will make -mlasx, -mlsx (implied),
> and -mlbt the default.  I prefer "-mlasx" over "-msimd=lasx" because "-
> mlasx" is shorter anyway (if there is no real reason to make -mlasx and
> -msimd=lasx two different things).

Perhaps just "--with-feature" or "--with-loongarch-feature", then we can
even fold -mstrict-align here, like "--with-feature=lbt,strict-align".


-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2023-08-14  6:01 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 [this message]
2023-08-14  8:44     ` Yujie Yang
2023-08-14  8:49       ` Xi Ruoyao
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=4c0e6470a94d01017d631f4255e0382840c7a2e8.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).