gentooLTO VS linux

You can also go full lto, see ltoize on https://github.com/InBetweenNames/gentooLTO.

If you want to optimize the living shit out of Gentoo, I'd advise not just stopping at LTO and -fdevirtualize-at-ltrans and checking out GentooLTO.

I am wondering if you prefer Clang or GCC. Which one compiles faster, and which one produces faster binaries? What are the advantages of Clang over GCC, and vice versa? I've enabled LTO optimizations for my system.

I unironically do that, see GentooLTO

EDIT: here you can check out it better.

Are you using LTO? Quick google found: https://github.com/InBetweenNames/gentooLTO/issues/139

FWIW I just based the joke off the GentooLTO project

> Torvalds answered that, while he used to find problems in the LLVM Clang compiler, now he's more likely to find problems with GCC instead; he now builds with Clang.

https://github.com/ClangBuiltLinux/linux/issues is our bug tracker for known issues (a few are tracked in llvm's issue tracker). Bug reporters and future kernel hackers wanted!

As I mentioned on mastodon, there's lots of bugs still to be fixed everywhere, but even if we don't fix them, providing competition in the toolchain space has been worth it to users.

Linux builds on clang after a decade of dedicated effort to make it happen, and that is with clang overall being comparatively similar to gcc (e.g clang implements many gcc extensions): https://github.com/ClangBuiltLinux/linux/wiki/Project-histor...

We got plenty of bugs for building the kernel with LLVM, if you're looking for tasks, pick one!

There's an semi-official github[0] for this.

AFAICT from the issue, Clang and binutils/LLVM tools work fine with no patches for the mainstream archs and when not trying to be super-fancy with custom flags. The more non-mainstream one goes with arch or flags the more likely one will run into something.

[0] https://github.com/ClangBuiltLinux/linux/issues

If you have any reproducible issues please file them here: https://github.com/ClangBuiltLinux/linux/issues

See if you can build your distro's config. make LLVM=1 localmodconfig olddefconfig bzImage. Any warnings? Any warnings not in the issue tracker? If not, pick one from the issue tracker and see if you can reproduce it. Note: lots of issues are tagged by target ISA, so you'll need to get familiar with cross compiling (setting ARCH= and CROSS_COMPILE=.

It's a pipeline; clang starts, hands off to LLVM.

For a compilation to object file from source code, the vast majority of time for most translation units is spent in the front end of the pipeline, not the middle, or backend.

See also my first plot: https://github.com/ClangBuiltLinux/linux/issues/1086#issueco...