> 2023年4月19日 23:15，Thomas Bogendoerfer <tsbogend@xxxxxxxxxxxxxxxx> 写道： > > On Wed, Apr 19, 2023 at 02:35:02PM -0700, Nick Desaulniers wrote: >> On Wed, Apr 19, 2023 at 9:50 AM Jiaxun Yang <jiaxun.yang@xxxxxxxxxxx> wrote: >>> >>> >>> >>>> 2023年4月18日 21:07，Nick Desaulniers <ndesaulniers@xxxxxxxxxx> 写道： >>>> >>>> On Fri, Apr 14, 2023 at 1:07 AM Jiaxun Yang <jiaxun.yang@xxxxxxxxxxx> 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@xxxxxxxxxx> >>>>> Signed-off-by: Jiaxun Yang <jiaxun.yang@xxxxxxxxxxx> >>>> >>>> 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 > > mips32r5 On wikipedia’s “Imagination Technologies” section. > >> - r5500 > > mips4 > >> - rm5200 > > mips4 I think those are all R5000 derivatives? > >> - sb1 > > mips64r1 On wikipedia’s "Other designers” section. > > all information taken from datasheets. > >> - loongson* Loongson-1A/1B/1C: Claims to be MIPS32R2 but lacks FP64 and DIEI, so I’d say they are R1. Loongson2e/Loongson2f: MIPS-III Loongson64: MIPS64R2 Thanks. - Jiaxu > > probably depends on the exact type, but as I don't have datasheets > I can't say what it is exactly, probaly mips32r2/mips64r2. > > Thomas. > > -- > Crap can work. Given enough thrust pigs will fly, but it's not necessarily a > good idea. [ RFC1925, 2.3 ]
