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]
Message-ID: <20241022200732.GA487584@thelio-3990X>
Date: Tue, 22 Oct 2024 13:07:32 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Koakuma <koachan@...tonmail.com>, Andreas Larsson <andreas@...sler.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"David S. Miller" <davem@...emloft.net>,
	Nick Desaulniers <ndesaulniers@...gle.com>,
	Bill Wendling <morbo@...gle.com>,
	Justin Stitt <justinstitt@...gle.com>, glaubitz@...sik.fu-berlin.de,
	Nicolas Schier <nicolas@...sle.eu>, sparclinux@...r.kernel.org,
	linux-kernel@...r.kernel.org, llvm@...ts.linux.dev,
	linux-kbuild@...r.kernel.org
Subject: Re: [PATCH v2 0/2] sparc/build: Rework CFLAGS for clang compatibility

On Wed, Oct 23, 2024 at 04:10:01AM +0900, Masahiro Yamada wrote:
> I applied this patch set, but I still observe a build error.
...
> masahiro@zoe:~/workspace/linux-kbuild(kbuild)$ make
> LLVM=~/tools/llvm-latest/bin/  ARCH=sparc sparc64_defconfig all
...
> clang: error: unsupported argument '--undeclared-regs' to option '-Wa,'

Koakuma might know more than I do but I did not test either the
integrated assembler or the rest of the LLVM tools; I only tested clang
for CC. As far as I am aware, that has been where most of the effort in
llvm-project has been going and I think there are probably other fixes
that will be needed for the other tools. The command I tested was:

  $ make -skj"$(nproc)" \
         ARCH=sparc64 \
         CC=clang \
         CROSS_COMPILE=sparc64-linux-gnu- \
         LLVM_IAS=0 \
         mrproper defconfig all

I see this as more of a stepping stone series to make testing those
other components easier as time goes on, hence why I did not really
consider user facing documentation either like you brought up in the
other thread.

Cheers,
Nathan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ