Pale Moon x86-64 SSE2/AVX2

[Moonchild]

AVX‑512 builds? Would they make a difference when compared to AVX2?

As far as I know AVX-512 is just a wider version of AVX2, and it also becomes more complicated because there are many different flavours of AVX-512 (some with byte/word support, some without).
For a web browser and javascript where we don't really do much beyond 64-bit, it would likely make no difference aside from bumping power usage. It'll be oversized for our typical processing. Not like we're having large data structures that need very efficient processing; we're not doing AI, we don't do video encoding, etc. And even those tasks are more likely to take advantage of NPU or GPU so AVX-512 on the CPU is more of a niche than anything else that likely won't have any real-world positive impact (It might actually be worse than AVX2 because of the overhead)

[UCyborg]

I can't find the links again, but apparently some Linux users came up with unofficial SSE3 and 3DNow! builds of Pale Moon. I wonder how those would stack against SSE2 builds.

[Nuck-TH]

v34 builds are now available.

[karlchen]

Thank you very much, Moonchild and Nuck-TH.

Code: Select all

$ inxi -SCx3; palemoon --version
System:    Host: voyager Kernel: 5.15.0-164-generic arch: x86_64 bits: 64 compiler: gcc v: 11.4.0 clocksource: tsc
           Desktop: Cinnamon v: 6.0.4 tk: GTK v: 3.24.33 wm: Muffin v: 6.0.1 vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint
             21.3 Virginia base: Ubuntu 22.04 jammy
CPU:       Info: quad core model: Intel Core2 Quad bits: 64 type: MCP smt: <unsupported> arch: Core2 Merom rev: 7 cache:
             L1: 256 KiB L2: 8 MiB
           Speed (MHz): avg: 1595 min/max: 1600/2400 cores: 1: 1595 2: 1595 3: 1595 4: 1595 bogomips: 19139
           Flags-basic: ht lm nx pae sse sse2 sse3 ssse3 vmx
           
Moonchild Productions Pale Moon 34.0.0

[flamelord]

I was just about to make a thread complaining about auto-updates not working since I updated today manually and I thought auto-updates weren't workng correctly, only to sign up and look at the release notes and realize that it's been almost 3 months since the last update

[back2themoon]

Many thanks for the instant release.

[raid5]

Hi I'm updating an older machine on Windows 7 x64 which was on 29.0.1 originally.

I stepped through updating to each major release with no problem, then noticed the notes on v33 about AVX. Since that machine has a Core2 Duo it looks like it will not work with AVX builds.

Do I just need to install the v33 SSE2 build on top of the current v32 build? Then going forward do all updates from ftp2.palemoon.org/avx/ ?

Or is it not necessary because Win7 doesn't support or require AVX by default?


Thanks.

[billmcct]

I was just about to make a thread complaining about auto-updates not working since I updated today manually and I thought auto-updates weren't workng correctly, only to sign up and look at the release notes and realize that it's been almost 3 months since the last update

MC announced a delay in the new milestone.

[ron_1]

When checking the signature for 34 I keep getting this:

gpg: Signature made Tue 20 Jan 2026 11:48:16 AM EST
gpg: using RSA key 5061CC51C94306050CFA1FEE48FAD2907D84EDEB
gpg: Can't check signature: No public key

I made sure I have a gpg.conf file in .gnupg under home. I don't know what's wrong. I did an OS reinstall not too long ago, so that probably messed something up. Where is the .sig file supposed to go?

I also noticed I'm missing a trustdb.gpg file in there.

[ron_1]

Alright, I figured out I had to import the key. Now I got this, is it good to go? I'm wondering about the part that says "no public key for trusted key - skipped" and "ultimately trusted key 865E6C87C65285EC not found."

gpg: Signature made Tue 20 Jan 2026 11:48:16 AM EST
gpg: using RSA key 5061CC51C94306050CFA1FEE48FAD2907D84EDEB
gpg: key 865E6C87C65285EC: no public key for trusted key - skipped
gpg: key 865E6C87C65285EC marked as ultimately trusted
gpg: key 48FAD2907D84EDEB marked as ultimately trusted
gpg: checking the trustdb
gpg: Note: ultimately trusted key 865E6C87C65285EC not found
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: next trustdb check due at 2026-04-09
gpg: Good signature from "Nuck-TH <nuck*********@gmail.com>" [ultimate]

[back2themoon]

Do I just need to install the v33 SSE2 build on top of the current v32 build? Then going forward do all updates from ftp2.palemoon.org/avx/? Or is it not necessary because Win7 doesn't support or require AVX by default?

The Windows version is unrelated, it's all about the CPU. So yes, you only need to install the SSE2 build from the links in the first post.

Also note that these builds support auto-updating (to the correct build, of course) so you won't need to manually download and install every time.

[UCyborg]

I wonder which builds here get more downloads, AVX2 or SSE2?

[raid5]

Do I just need to install the v33 SSE2 build on top of the current v32 build? Then going forward do all updates from ftp2.palemoon.org/avx/? Or is it not necessary because Win7 doesn't support or require AVX by default?

The Windows version is unrelated, it's all about the CPU. So yes, you only need to install the SSE2 build from the links in the first post.

Also note that these builds support auto-updating (to the correct build, of course) so you won't need to manually download and install every time.

OK, great. Thank you very much.

[Moonchild]

The SSE2 and AVX2 versions for v34.0.1 have been released in tandem with mainline.

[ron_1]

Can someone tell me what the line below means? I get another line that says "marked as ultimately trusted" so I guess it passes the test, but I want to understand this gpg thing better. (Sorry for asking twice.)

Code: Select all

gpg: key 865E6C87C65285EC: no public key for trusted key - skipped

[Moonchild]

Can someone tell me what the line below means? I get another line that says "marked as ultimately trusted" so I guess it passes the test, but I want to understand this gpg thing better. (Sorry for asking twice.)

Code: Select all

gpg: key 865E6C87C65285EC: no public key for trusted key - skipped

It means that you have a PGP signature but don't have the public key of the key pair to check if it's a valid signature.

Nuck-TH will have to make sure the public key of his (I assume new) key pair is available, normally by uploading it to public key servers (or alternatively by posting it here so you can manually import it)

[Nuck-TH]

It was(and is) always posted in OP.

[Moonchild]

It was(and is) always posted in OP.

Seems like that key has expired though (2025-03-27). That's why I assumed you had created a new one?

[Nuck-TH]

Hm, yes, it is actually in this post.
If it is stale too then... whatever. I still haven't capacity to properly deal with this.

[Moonchild]

Hm, yes, it is actually in this post.
If it is stale too then... whatever. I still haven't capacity to properly deal with this.

It's not that difficult though? just generate a new key pair, sign it with your previous key to establish base trust. i'll be happy to sign it as well!