Message from @Goz3rr
Discord ID: 644529179118927892
>In this case the assembler update didn't make any difference as Firefox wasn't rebuilt from source as part of the test profile or the Clear Linux revision.
so normal usecase for home user ?
where ucode is applied but software is not update to match ?(or apt-get repo aint updated) ?
what do you mean normal use case
firefox has autoupdater
it'll be updated soon enough
windows 10 will get it updated too
yeah soon enough few days of slow speeds nobody notices :D
on a consumer level, there wont be anything much that exploit these vulnerabilities tbh
no slow speeds until the microcode update rolls out
true enough ~
however on the server cloud level, these vulnerabilities allows one to steal data
JCC errata is only fixing "undefined behaviour" atm
no published vuln
and not that firefox is the place where the speed is needed that much anyway
it's like the FDIV bug
gaming wont be hit by CPU performance since it's more GPU now
even when you try to make it cpu bound
are Intel shills in full force already
Is this gonna be like the LAST time this happened, where everyone insisted intel users would take like a 25% performance hit, but in reality it was negligible except in very specific, niche uses?
Intel users BTFO indeed
you almost seem like a sane person matt
None of these affect in games anyway
reason to care about these: none
performance impacts from the JCC errata are a slightly bigger deal than earlier patches
they impact user space programs, where as previous patches only affected the kernel and related transitions
i mean its large enough performance hit on those "niche cases" that people are more and more turning mitigation off on all plantforms
"to get mah speeds"
what is quite dangerous path
those niche cases can safely turn off mitigations
as long as you don't run untrusted code
so ..browser
yes because the average person that runs a database and a browser on the same hardware
<:pepelaugh:615974280706129941>
or just you know browser when it comes to those older intel issues
the fucking POC was delivered in javascript
but no, even if you run a browser you can turn off mitigations without huge risk