@monarc99
"using AVX instructions infrequently could degrade performance or power efficiency"
https://stackoverflow.com/questions/52653025/why-is-march-native-used-so-rarely
Git Clone URL: | https://aur.archlinux.org/ungoogled-chromium.git (read-only, click to copy) |
---|---|
Package Base: | ungoogled-chromium |
Description: | A lightweight approach to removing Google web service dependency |
Upstream URL: | https://github.com/ungoogled-software/ungoogled-chromium |
Keywords: | blink browser privacy web |
Licenses: | BSD-3-Clause |
Conflicts: | chromedriver, chromium |
Provides: | chromedriver, chromium |
Submitter: | ilikenwf |
Maintainer: | JstKddng (networkException) |
Last Packager: | networkException |
Votes: | 353 |
Popularity: | 3.75 |
First Submitted: | 2016-12-19 08:08 (UTC) |
Last Updated: | 2024-12-20 12:47 (UTC) |
« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 66 Next › Last »
@monarc99
"using AVX instructions infrequently could degrade performance or power efficiency"
https://stackoverflow.com/questions/52653025/why-is-march-native-used-so-rarely
i use for my private builds on my newer notebook (with avx2 support):
CFLAGS="-march=native -mtune=native -O3 -pipe -fno-plt"
for my old desktop (pre AVX2) pc, i had to switch back to
CFLAGS="-march=x86-64-v2 -mtune=native -O3 -pipe -fno-plt"
there a avx2 instructions in tensorflow (to test, if the cpu support avx2), and the compiler is confused, to compile avx2 instructions, when -march=native disables avx2.
and i enable PGO: in PKGBUILD before the CFLAGS settings:
# enable pgo
_linux_pgo_file=$(cat chrome/build/linux.pgo.txt)
if [ ! -f "chrome/build/pgo_profiles/${_linux_pgo_file}" ]; then
msg2 'Downloading pgo_profiles data'
curl "https://storage.googleapis.com/chromium-optimization-profiles/pgo_profiles/${_linux_pgo_file}" --output "chrome/build/pgo_profiles/${_linux_pgo_file}"
fi
_flags+=(
'chrome_pgo_phase=2'
'is_clang=true'
'use_lld=true'
)
and that could hurt performance on intel cpus.
Not only that, it would most likely segfault on other (micro)architectures due to unknown instructions.
@followait
you can certainly try adding it to your builds but I wouldn't add it here as the repo builds would be optimized for the architecture the OBS uses for compiling (amd epyc iirc) and that could hurt performance on intel cpus.
For GCC and clang, what about adding option "-march=native", which also implies "-mtune=native"?
How much performance can it boost?
On one of my devices, I get the following error:
[4041/49178] ACTION //third_party/blink/public/moj...sage_ids(//build/toolchain/linux/unbundle:default)ninja: error: WriteFile(__third_party_blink_public_mojom_memory_usage_monitor_linux_mojo_bindings__generate_message_ids___build_toolchain_linux_unbundle_default__rule..rsp): Unable to create file. File name too long
Maybe this could be caused through /tmp being mounted on the drive as opposed to a ramdisk? Versions up 'til 91 installed fine, just fine, though.
Any thoughts?
@unphysicalix
yes it's ok, just click on the Flag package out-of-date
button. I'll update asap
Hi, is it ok to remind you of a 3 day old newer version ? https://github.com/Eloston/ungoogled-chromium/releases/tag/94.0.4606.81-1
A new PKGBUILD will be appreciated. Thanks.
Sorry - typo. I just meant clang 12
, had only confused that with gcc 11
. Sorry again. chromium
comes with clang 13
, and apparently, there are a few differences.
Pinned Comments
JstKddng commented on 2022-05-06 14:37 (UTC) (edited on 2022-06-27 13:48 (UTC) by JstKddng)
A new va-api patch for wayland has been added. Required flags for it to work are the following, thanks to @acidunit
JstKddng commented on 2020-07-19 06:34 (UTC)
You can get prebuilt binaries here:
https://github.com/ungoogled-software/ungoogled-chromium-archlinux#binary-downloads
seppia commented on 2018-12-12 21:34 (UTC)
Please do NOT flag this package as out of date in relation to official chromium releases.
This is NOT Google Chromium and new releases come after additional work of the ungoogled-chromium contributors, so they may not be ready, nor available for days or even weeks after a new version of official chromium is released.
Please refer to https://github.com/Eloston/ungoogled-chromium/tags for ungoogled-chromium releases. Use those and please flag this package as out of date only if a newer release is present there. I will update the PKGBUILD as soon as I can every time a new release comes out.
Thanks