linux-kernel - Re: [PATCH] sparc/build: Make all compiler flags also clang-compatible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Sun, 23 Jun 2024 18:53:37 +0200
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: koachan@...tonmail.com, "David S. Miller" <davem@...emloft.net>, Andreas
 Larsson <andreas@...sler.com>, Nathan Chancellor <nathan@...nel.org>, Nick
 Desaulniers <ndesaulniers@...gle.com>, Bill Wendling <morbo@...gle.com>,
 Justin Stitt <justinstitt@...gle.com>
Cc: sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org, 
	llvm@...ts.linux.dev
Subject: Re: [PATCH] sparc/build: Make all compiler flags also
 clang-compatible

Hi Koakuma,

On Thu, 2024-06-20 at 22:56 +0700, Koakuma via B4 Relay wrote:
> - More trivial is to change `-mv8plus` -> `-mcpu=v9`.
>   This should be safe too since the kernel seems to require a V9
>   processor to run anyway, so I'm changing the flag to one that is
>   portable between GCC and clang.

I just looked up what the exact difference between V8plus and 32-bit
V9 is and it turns out it's not exactly the same [1].

V8plus does not use VIS instructions and also has a different ELF machine
type, namely EM_SPARC32PLUS instead of EM_SPARCV9 if I understand correctly.

So, we should make sure that the above change will not affect the ELF machine
type.

Adrian

> [1] https://stackoverflow.com/questions/23506538/what-is-em-sparc32plus-for

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913