{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidm2pgaypfypkevd72mt7nsvrjeuq5to5dem6cy3vuy7f3sslzwwm",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mie2qeq2ez32"
  },
  "path": "/viewtopic.php?t=33248&p=271643#p271643",
  "publishedAt": "2026-03-31T01:57:33.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://repo.dactyloidae.xyz/Dactyloida ... 871b8be379",
    "https://www.felixcloutier.com/x86/movhlps"
  ],
  "textContent": "> > Does it? Looked at this commit: https://repo.dactyloidae.xyz/Dactyloida ... 871b8be379\n> Using `vmovhlps` with 3 parameters, which means AVX, but you just check it with SSE2. Ref: https://www.felixcloutier.com/x86/movhlps\n>\n> If these code go upstream, these are needed to be clarified.\n>\n> This kind of thing is actually a part of _why_ we made AVX the baseline instead of SSE2. AVX instructions are useful for improving performance, and honestly it's easy to get mixed up and pull in AVX instructions as part of an optimization when you think you're staying well within SSE/SSE2 territory. Just making AVX the baseline means you don't have to worry as much and can just focus on using optimized instructions.\n\nIt could be fine if it is guarding correctly, at least it won't crash when using it on pre-AVX processors. (while old code benefits older processors that has SSE3 but not AVX)\n\nAnd to me, commits like this are mixing up in various purposes and it should be better to separated if these changes are going to upstream.\n\n* * *",
  "title": "Other Applications • Re: Dactyloidae Browser (Basilisk fork)",
  "updatedAt": "2026-03-31T01:57:33.000Z"
}