home.social

#sse4 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #sse4, aggregated by home.social.

  1. For those who missed it, there is an ongoing discussion on the Github about whether to drop support for SSE4 in favor of performance improvements and better maintainability. So far the strong consensus is to drop SSE4 but retain support for AVX1, but if you have a fresh perspective to offer, please join in. github.com/PCSX2/pcsx2/issues/

    PS: PCSX2 contributor Stenzek mentioned "AVX-512" a couple times. Wonder what that's all about. 👀 #pcsx2 #sse4 #emulation

  2. For those who missed it, there is an ongoing discussion on the Github about whether to drop support for SSE4 in favor of performance improvements and better maintainability. So far the strong consensus is to drop SSE4 but retain support for AVX1, but if you have a fresh perspective to offer, please join in. github.com/PCSX2/pcsx2/issues/

    PS: PCSX2 contributor Stenzek mentioned "AVX-512" a couple times. Wonder what that's all about. 👀 #pcsx2 #sse4 #emulation

  3. For those who missed it, there is an ongoing discussion on the Github about whether to drop support for SSE4 in favor of performance improvements and better maintainability. So far the strong consensus is to drop SSE4 but retain support for AVX1, but if you have a fresh perspective to offer, please join in. github.com/PCSX2/pcsx2/issues/

    PS: PCSX2 contributor Stenzek mentioned "AVX-512" a couple times. Wonder what that's all about. 👀 #pcsx2 #sse4 #emulation

  4. For those who missed it, there is an ongoing discussion on the Github about whether to drop support for SSE4 in favor of performance improvements and better maintainability. So far the strong consensus is to drop SSE4 but retain support for AVX1, but if you have a fresh perspective to offer, please join in. github.com/PCSX2/pcsx2/issues/

    PS: PCSX2 contributor Stenzek mentioned "AVX-512" a couple times. Wonder what that's all about. 👀 #pcsx2 #sse4 #emulation

  5. Some of y'all to let those Ivy bridge and Sandy bridge systems retire. So close to ubiquitous support for #AVX2, but not quite high enough to make it the de facto minimum across programs.

    Thankfully #SSE4 is at 99.55%, enough to retire SSE2 only code paths

    Data from the latest Steam HW survey: store.steampowered.com/hwsurve

  6. Some of y'all to let those Ivy bridge and Sandy bridge systems retire. So close to ubiquitous support for #AVX2, but not quite high enough to make it the de facto minimum across programs.

    Thankfully #SSE4 is at 99.55%, enough to retire SSE2 only code paths

    Data from the latest Steam HW survey: store.steampowered.com/hwsurve

  7. Some of y'all to let those Ivy bridge and Sandy bridge systems retire. So close to ubiquitous support for #AVX2, but not quite high enough to make it the de facto minimum across programs.

    Thankfully #SSE4 is at 99.55%, enough to retire SSE2 only code paths

    Data from the latest Steam HW survey: store.steampowered.com/hwsurve

  8. Some of y'all to let those Ivy bridge and Sandy bridge systems retire. So close to ubiquitous support for #AVX2, but not quite high enough to make it the de facto minimum across programs.

    Thankfully #SSE4 is at 99.55%, enough to retire SSE2 only code paths

    Data from the latest Steam HW survey: store.steampowered.com/hwsurve

  9. Some of y'all to let those Ivy bridge and Sandy bridge systems retire. So close to ubiquitous support for #AVX2, but not quite high enough to make it the de facto minimum across programs.

    Thankfully #SSE4 is at 99.55%, enough to retire SSE2 only code paths

    Data from the latest Steam HW survey: store.steampowered.com/hwsurve