Arch Linux User Repository

This package has been revised to use the variant corresponding to architecture set in some config files. This may cause problems with other packages, so users choosing to do this are (mostly) on their own.

• makepkg.conf — CARCH="x86_64_v3" (or v2)
• pacman.conf — Architecture = auto x86_64 x86_64_v2 x86_64_v3
• /usr/share/devtools/setarch-aliases.d/x86_64_v3 — Contents: x86_64

The default variant is SSE3. This version is the closest available to baseline x86_64, which is currently the only architecture supported by Arch Linux. Other variants have shown no significant performance benefit, while crashing on some users' computers. The default will not be changed unless upstream offerings change or there is no other way to prevent a significant bug. Please refrain from arguing to change default for any other reason.

Alternate PKGBUILDs are available (i386, sse3, sse4, avx, avx2). They may be used by running makepkg -Cp <file>. This is the recommended way to build alternate versions to avoid interfering with other packages.

• This package no longer attempts to autoupdate.

  • Skipping the beta builds for now.
  • Check for new releases at Alex313031/thorium.

• Avoid flagging and commenting at the same time for the same issue.

  • Flag for common issues with standard solutions.
  • Comment for issues requiring explanation or debugging.
  • Use a pastebin for blocks of text more than a few lines.

@nrw2001 I updated the pinned comment after seeing your previous comment.

i apologize i noticed your pinned comment and fixed my noob mistake already thanks for the correction on etiquette

recent beta release seems to have broken your package. I love this browser thank you for your contribution

source "thorium-browser_126.0.6478.231_SSE3.deb" tries to call "==> ERROR: Failure while downloading https://github.com/Alex313031/Thorium/releases/download/M126.0.6478.246/thorium-browser_126.0.6478.246_SSE3.deb" wich is a beta release "thorium-browser_126.0.6478.246_Th24_SSE4.deb" and seems to be sse4 only no sse3 option

Having accidentally discovered this project and seen the results of comparing different optimizations, I wanted to write a comment. These are exclusively my observations, perhaps they will be useful. I am also a fan of forcing compilation flags ;)

I played with gzip with different build flags on the same test file and the difference in speed was several percents. My processor can only do SSE4.1 , but according to my friend, there is a difference between SSE3 and AVX in this experimet, although small and in favor of AVX.

When building the Linux kernel, attempts to set the desired compiler flags from the outside fail. The reason for this is that the build scripts reassign them during operation. It is possible that same applies to Chromium too. The only successful example when this works for the Linux kernel is when I replace all -O2 with "-O2 and desired flags" in all makeconfigs. When I force the use of SIMD instructions in this way, the kernel becomes inoperative. There, in one of the kernel build scripts where simds are specifically disabled for this reason, and contain a corresponding warning.

By themselves, -msse3 and etc. have little effect. In my experiments: unrolling loops may speed up only some specific loops and slows down all other code; simplifying loops, moving conditions outside the loop, reducing the use of stack and registers, ftracer, prefetch, autovectorization and autosimdization give the most performance gain. The corresponding gcc flags are in its manual. vlc, mpv, inkscape and even ffmpeg with its assembler code fragments works a little bit faster with this.. well, on my core2duo like cpu and armv7 linux-box.

@adamjonn 32-bit version should already be blacklisted. You either need to resync the pkgbuild or clear cache.

it seems to be picking up the wrong file since now the 32bit version has been added to the repo so now the update fails.

i can do it myself with the below but prefer it to update via aur.

thorium=$(curl -L https://api.github.com/repos/Alex313031/Thorium/releases/latest -s) thorlink=$(grep -oP '(?<="browser_download_url": ")[^"]*' <<< "$thorium" | grep _SSE3.deb)

@jronald That is outside the scope of packaging. From the readme, some patches from ungoogled chromium are already included. If that isn't enough, you can open an issue upstream. However, I doubt you're likely to convince the developer to drop features he actually uses.

What about ungoogling it like ungoogled-chromium?