mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: llvm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: Slim and optimized LLVM toolchains for building the Linux kernel
Date: Tue, 28 Mar 2023 12:09:06 -0700	[thread overview]
Message-ID: <20230328190906.GB375033@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20230319235619.GA18547@dev-arch.thelio-3990X>

On Sun, Mar 19, 2023 at 04:56:21PM -0700, Nathan Chancellor wrote:
> Hi everyone,
> 
> To make building the Linux kernel with clang/LLVM easier and more
> accessible to people (since distributions tend to only package one
> version at a time and it may be old or have bugs that have since been
> fixed), I have uploaded some slim, profile guided optimized LLVM toolchains
> to my section of kernel.org/pub:
> 
> https://mirrors.edge.kernel.org/pub/linux/kernel/people/nathan/llvm/

This is now

https://mirrors.edge.kernel.org/pub/tools/llvm/

so that they are no longer tied directly to my kernel.org account. I
have updated the README with additional information based on feedback
that I have received thus far.

> The landing page should have all the relevant information but if I need
> to clarify or expand on anything, I am more than happy to do so.
> 
> Due to benchmarking the compilers against the kernel during PGO, they
> can handily beat distribution versions that have not been optimized:
> 
> https://gist.github.com/nathanchance/8d1abed70077ac92cb198ef32389072e
> 
> I aim to keep these up to date with the latest stable versions of LLVM
> as they are released (so 16.0.0 will be replaced with 16.0.1 when it is
> released, etc).

Cheers,
Nathan

      reply	other threads:[~2023-03-28 19:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 23:56 Nathan Chancellor
2023-03-28 19:09 ` Nathan Chancellor [this message]

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=20230328190906.GB375033@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    /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®