mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	elver@google.com, linux-kernel@vger.kernel.org,
	bigeasy@linutronix.de, mingo@kernel.org, tglx@linutronix.de,
	will@kernel.org, boqun.feng@gmail.com, longman@redhat.com,
	hch@lst.de, rostedt@goodmis.org, llvm@lists.linux.dev
Subject: Re: [RFC][PATCH 0/4] locking: Add/convert context analysis bits
Date: Thu, 22 Jan 2026 11:58:12 -0700	[thread overview]
Message-ID: <20260122185812.GB3461196@ax162> (raw)
In-Reply-To: <d399e354-6d42-488e-a0b7-fe8d08b9bf34@acm.org>

On Thu, Jan 22, 2026 at 08:28:44AM -0800, Bart Van Assche wrote:
> The build-kernel-with-clang script is as follows (this may not be the
> recommended way to build the kernel with clang):
> 
> #!/bin/bash
> export CC=clang
> export LD=ld.lld      # Use LLVM's linker (optional but recommended)
> export AR=llvm-ar
> export NM=llvm-nm
> export OBJCOPY=llvm-objcopy
> export OBJDUMP=llvm-objdump
> export STRIP=llvm-strip
> export READELF=llvm-readelf
> make LLVM=1 CC=clang "$@"

FWIW, this could ultimately simplify to

    make LLVM=1 "$@"

as LLVM=1 is the shorthand for

    make CC=clang LD=ld.lld AR=llvm-ar NM=llvm-nm STRIP=llvm-strip \
         OBJCOPY=llvm-objcopy OBJDUMP=llvm-objdump READELF=llvm-readelf \
         HOSTCC=clang HOSTCXX=clang++ HOSTAR=llvm-ar HOSTLD=ld.lld

as noted in Documentation/kbuild/llvm.rst /
https://docs.kernel.org/kbuild/llvm.html.

Cheers,
Nathan

  reply	other threads:[~2026-01-22 18:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 11:07 Peter Zijlstra
2026-01-21 11:07 ` [RFC][PATCH 1/4] compiler-context-analysys: Add __cond_releases() Peter Zijlstra
2026-01-21 13:09   ` Marco Elver
2026-01-21 17:55   ` Bart Van Assche
2026-01-21 18:35     ` Marco Elver
2026-01-21 19:02       ` Peter Zijlstra
2026-01-21 21:02         ` Bart Van Assche
2026-03-09 19:48   ` [tip: locking/core] " tip-bot2 for Peter Zijlstra
2026-01-21 11:07 ` [RFC][PATCH 2/4] locking/mutex: Add context analysis Peter Zijlstra
2026-01-21 17:11   ` Bart Van Assche
2026-01-21 18:59     ` Peter Zijlstra
2026-03-09 19:48   ` [tip: locking/core] " tip-bot2 for Peter Zijlstra
2026-01-21 11:07 ` [RFC][PATCH 3/4] locking/rtmutex: " Peter Zijlstra
2026-01-21 17:15   ` Bart Van Assche
2026-01-21 19:01     ` Peter Zijlstra
2026-03-09 19:48   ` [tip: locking/core] " tip-bot2 for Peter Zijlstra
2026-01-21 11:07 ` [RFC][PATCH 4/4] futex: Convert to compiler " Peter Zijlstra
2026-01-21 13:19   ` Peter Zijlstra
2026-03-18  8:02   ` [tip: locking/core] " tip-bot2 for Peter Zijlstra
2026-01-21 13:07 ` [RFC][PATCH 0/4] locking: Add/convert context analysis bits Marco Elver
2026-01-21 19:23 ` Peter Zijlstra
2026-01-21 20:37   ` Bart Van Assche
2026-01-22  9:04     ` Peter Zijlstra
2026-01-22 16:28       ` Bart Van Assche
2026-01-22 18:58         ` Nathan Chancellor [this message]
2026-01-23 11:06           ` Peter Zijlstra
2026-01-23 11:15         ` Peter Zijlstra
2026-01-23 18:58           ` Bart Van Assche
2026-01-23 20:15             ` Marco Elver
2026-01-23 14:16   ` Sebastian Andrzej Siewior

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=20260122185812.GB3461196@ax162 \
    --to=nathan@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=boqun.feng@gmail.com \
    --cc=bvanassche@acm.org \
    --cc=elver@google.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=longman@redhat.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®