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.

@RubenKelevra Decision has already been made. You have provided no evidence to support making any changes, and you're asking questions that have already been answered. A PKGBUILD to package the AVX2 version is already available. You're free to use it or not. Please do not comment further unless you have a legitimate packaging issue to report.

@xiota all browsers use AVX/AVX2 optimizations for media decoding. Those are usually programmed in assembler and are used if the CPU supports it.

So I would be surprised if the SSE3 build wouldn't contain AVX/AVX2 instructions - but that's not really what a SSE3 vs AVX/AVX2 build is about: Giving the compiler the ability to use AVX/AVX2 instructions, where it seems fitting.

I understand if you want to support SSE3 CPUs, which is fine. But why not create a thorium-browser-bin-sse3 package for this?

I think the default should be what upstream provides, with most optimizations on.

There used to be separate SSE3 and AVX2 packages on AUR. Maintaining separate packages wasn't worth the effort given the undetectable performance difference of the AVX2 version in return for crashing on some users' computers.

There is a reason there is no performance benefit. Probably why Mozilla and Google do not target AVX/AVX2, which is that they do. You can use aur/intelxed to see that the SSE3 build contains AVX2 instructions.

@RubenKelevra The world does not revolve around you snowflake. Nothing stopping you from building it yourself if you are so smart.... He made a fast and extremely stable package which in his opinion is the most compatable version for most use cases. I agree. You are allowed your opinion to but we don't have to validate your opinion. He told you how to get what you want. Dry your tears and listen and do the work. You may even learn something in the process.

@xiota keep up the good work! And thank you very much!

I've already read it before commenting, but sounds like "works for me". AVX2 might make no difference for the test you ran on one computer, but this doesn't mean it doesn't have benefits outside of this test, and on other CPUs.

And yeah, there might be people rocking SSE3 CPUs, but there's also plenty of people with AVX2.

Why not make AVX2 the default, and have people with legacy hardware execute the PKGBUILD.sse3 - or simply split up the package?

@RubenKelevra Read pinned comment. No performance benefit from AVX builds.

Read old comments. Plenty of people still use computers that do not work with AVX builds.

Why do you use slow SSE3 builds? Please use the AVX2 ones, were not in 2012.