{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia6vwt5u7opvooiglzxjculqfqw5djnmrheslemf6nhawsuxb5zri",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mngtxh3552y2"
  },
  "path": "/viewtopic.php?t=32780&p=275196#p275196",
  "publishedAt": "2026-06-04T04:13:29.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> The way I handled the Dav1d was to use the new configure option \"--enable-libaom\" by default only on SSE2 builds. I added an environment variable to allow the user to override the defaults, enabling use of Dav1d on SSE2 or AOM on AVX, if so desired.\n>\n> Based on the release notes, this seemed like a safe/sane way to approach it, but I'm open to suggestions.\n\nWell, the issue is kind of that Dav1d doesn't actually work on SSE2-only CPUs, at least not if it's compiled on a machine that has AVX instructions available. The issue seems to be that it emits AVX instructions on any compiler/machine combo that can, regardless of what you want. Hypothetically, it might work if you compile it on a machine with a CPU that can't support AVX, because that would force the compiler to generate fallback instructions or something, but I have no idea.\n\n* * *",
  "title": "Contributed 3rd Party Builds • Re: Pale Moon for Slackware Linux",
  "updatedAt": "2026-06-04T04:13:29.000Z"
}