From: Nick Desaulniers <ndesaulniers@google.com>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
llvm@lists.linux.dev, Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v2 6/7] MIPS: Fallback CPU -march CFLAG to ISA level if unsupported
Date: Wed, 19 Apr 2023 14:35:02 -0700 [thread overview]
Message-ID: <CAKwvOd=sNyOq9J=CS09XXQ6YY3y3ytLnwHxKoHNdddcxYk=nJQ@mail.gmail.com> (raw)
In-Reply-To: <550FCA0F-2C48-4133-85B0-D9494CC1C23C@flygoat.com>
On Wed, Apr 19, 2023 at 9:50 AM Jiaxun Yang <jiaxun.yang@flygoat.com> wrote:
>
>
>
> > 2023年4月18日 21:07,Nick Desaulniers <ndesaulniers@google.com> 写道:
> >
> > On Fri, Apr 14, 2023 at 1:07 AM Jiaxun Yang <jiaxun.yang@flygoat.com> wrote:
> >>
> >> LLVM does not implement some of -march options. However those options
> >> are not mandatory for kernel to build for those CPUs.
> >>
> >> Fallback -march CFLAG to ISA level if unsupported by toolchain so
> >> we can get those kernel to build with LLVM.
> >>
> >> Link: https://github.com/ClangBuiltLinux/linux/issues/1544
> >> Reported-by: Nathan Chancellor <nathan@kernel.org>
> >> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> >
> > Thanks for the patch! Maybe it's more obvious to folks who work on
> > mips, but how did you determine that say `p5600` is `mips32r5` or
> > `r10000` is `mips4`?
>
> Wikipedia [1] should fit the purpose.
>
> [1]: https://en.wikipedia.org/wiki/List_of_MIPS_architecture_processors
Mostly! Though I was not able to verify:
- p5600
- r5500
- rm5200
- sb1
- loongson*
The rest LGTM, but maybe these families are better understood by Thomas?
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2023-04-19 21:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 8:06 [PATCH v2 0/7] MIPS: LLVM toolchain support for more CPUs Jiaxun Yang
2023-04-14 8:06 ` [PATCH v2 1/7] MIPS: Move various toolchain ASE check to Kconfig Jiaxun Yang
2023-04-14 8:06 ` [PATCH v2 2/7] MIPS: Add toolchain feature dependency for microMIPS smartMIPS Jiaxun Yang
2023-04-18 13:08 ` Thomas Bogendoerfer
2023-04-19 23:01 ` Nick Desaulniers
2023-04-20 19:41 ` Jiaxun Yang
2023-04-24 17:03 ` Nathan Chancellor
2023-04-14 8:06 ` [PATCH v2 3/7] MIPS: Detect toolchain support of workarounds in Kconfig Jiaxun Yang
2023-04-18 13:09 ` Thomas Bogendoerfer
2023-04-18 17:14 ` Jiaxun Yang
2023-04-14 8:06 ` [PATCH v2 4/7] MIPS: Detect toolchain support of o32 ABI with 64 bit CPU Jiaxun Yang
2023-04-14 8:06 ` [PATCH v2 5/7] MIPS: Remove cc-option checks for -march=octeon Jiaxun Yang
2023-04-14 8:07 ` [PATCH v2 6/7] MIPS: Fallback CPU -march CFLAG to ISA level if unsupported Jiaxun Yang
2023-04-18 20:07 ` Nick Desaulniers
2023-04-19 16:50 ` Jiaxun Yang
2023-04-19 21:35 ` Nick Desaulniers [this message]
2023-04-19 22:15 ` Thomas Bogendoerfer
2023-04-19 23:36 ` Jiaxun Yang
2023-04-20 8:06 ` Thomas Bogendoerfer
2023-04-20 16:32 ` Nick Desaulniers
2023-04-20 18:42 ` Xi Ruoyao
2023-04-20 18:50 ` Xi Ruoyao
2023-04-20 19:16 ` Jiaxun Yang
2023-04-14 8:07 ` [PATCH v2 7/7] MIPS: Limit MIPS_MT_SMP support by ISA reversion Jiaxun 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='CAKwvOd=sNyOq9J=CS09XXQ6YY3y3ytLnwHxKoHNdddcxYk=nJQ@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.