Skip to content

Chromium browser compiled with the Clang/LLVM compiler.

Notifications You must be signed in to change notification settings

RobRich999/Chromium_Clang

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 

Repository files navigation

Chromium_Clang:

The Chromium web browser for Windows and Linux built with the open source Clang compiler and LLD linker.

Additional features of the builds include modified compiler and linker optimizations via build configuration modifications.

Implementation of various options are subject to change depending upon performance, stability, and similar paramaters.


Links to latest Linux build releases in deb package format:

https://github.com/RobRich999/Chromium_Clang/releases/tag/v133.0.6836.0-r1382377-linux64-deb-avx

https://github.com/RobRich999/Chromium_Clang/releases/tag/v133.0.6836.0-r1382377-linux64-deb-avx2

https://github.com/RobRich999/Chromium_Clang/releases/tag/v133.0.6836.0-r1382377-linux64-deb-avx2-znver2


Links to latest Windows build releases:

https://github.com/RobRich999/Chromium_Clang/releases/tag/v132.0.6805.0-r1374882-win64-avx

https://github.com/RobRich999/Chromium_Clang/releases/tag/v133.0.6836.0-r1382581-win64-avx2

https://github.com/RobRich999/Chromium_Clang/releases/tag/v133.0.6836.0-r1382329-win64-avx512

Chromium_Clang for Windows builds are cross-compiled under Linux.


Optimization-related build tags:

Builds marked with the "+fulllto" tag utilize whole-program analysis and cross-module optimization using "full" link time optimization.

Builds marked with the "+thinlto" tag utilize whole-program analysis and cross-module optimization using "thin" link time optimization.

Builds marked with the "+pgo" tag utilize profile-guided optimization.

Builds marked with the "+polly" tag utilize the Polly "high-level loop and data-locality optimizer and optimization infrastructure for LLVM."

Builds marked with the "+fast-math" tag utilize aggressive floating-point optimizations for various hot code paths.

Builds marked with the "+avx" tag require processors with AVX instruction set support.

Builds marked with the "+avx2" tag require processors with AVX2 instruction set support.

Builds marked with the "+avx512" tag require processors with AVX512 instruction set support.

Builds marked with the "+amd_znver2" tag are AVX2 builds tuned for the AMD Zen 2 processor microarchitecture.

Builds marked with the "+fma" tag require processors with FMA instruction set support.

Builds marked with the "+sse2" tag (deprecated) require processors with SSE2 instruction set support. AVX support is not required.

Builds marked with the "+sse3" tag (deprecated) require processors with SSE3 instruction set support. AVX support is not required.

SSE3 support is the Chromium project's own minimum SIMD requirement on x86 platforms as of v89 builds.


Primary reason for AVX/AVX2 build recommendation:

https://johnk.dev/blogs/generated/vex-transition-penalties.html


Note regarding FFmpeg:

Use the javascript patcher from here...

https://github.com/StaZhu/enable-chromium-hevc-hardware-decoding

....along with the same repo's /third_party/webtrc patch...

enable-h26x-packet-buffer-by-default.patch

...then proceed with the Chromium_Clang patches and build arguments.


Typical third-party build disclaimer. No warranties. No guarantees. Your mileage may vary. Use at your own risk.