linux-kernel - [sparc] Use of -fcall-used-* flags in Makefile?

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-next>] [day] [month] [year] [list]

Message-ID: <JAYB7uS-EdLABTR4iWZdtFOVa5MvlKosIrD_cKTzgeozCOGRM7lhxeLigFB1g3exX445I_W5VKB-tAzl2_G1zCVJRQjp67ODfsSqiZWOZ9o=@protonmail.com>
Date: Sat, 16 Mar 2024 14:59:42 +0000
From: Koakuma <koachan@...tonmail.com>
To: "sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: "davem@...emloft.net" <davem@...emloft.net>, "ndesaulniers@...gle.com" <ndesaulniers@...gle.com>, "arnd@...db.de" <arnd@...db.de>
Subject: [sparc] Use of -fcall-used-* flags in Makefile?

Hello, first time poster so apologies if I posted to the wrong list.

Anyone knows why the SPARC makefiles (arch/sparc/Makefile and
arch/sparc/vdso/Makefile) set `-fcall-used-g5` and  `-fcall-used-g7`
in their CFLAGS?
Would it be safe if the kernel is compiled without those flags?

The context is that there's an effort to make the sparc64 kernel build
under LLVM/clang, and if possible we'd like to build the kernel without
those flags, at least when building with clang, since it simplifies
a lot of things on the LLVM side.
(LLVM tracker: https://github.com/llvm/llvm-project/issues/40792)