Message from @Goz3rr
Discord ID: 644526835597836310
the problem this tweet is talking about
compilers can know about this issue and generate different code
to avoid crossing 32 byte boundaries or ending up on a 32 byte boundary
for negligible side effects (basically just add a nop or reorder code)
but the problem is
everything has to be recompiled for that to happen
hence things compiled before now might try to do that and see reduced performance
and the way almost all modern software works
no one actually compiles for different cpus
unless you're some arch turboautist
gentoo*
Same difference
it's not, you don't build from source on arch unless outside package manageer
Performance in games seems to be in line with the 0-4% decrease Intel states
Mainly because games are GPU limited anyways
INTEL NO 1
>when desktop CPUs are more powerful than your 10 times more expensive server CPUs
LOL!
>actually taking passmark as a representative benchmark
LOL!
you're laughing now until you realize that with the current going AMD users will get the same performance impact
yeah when that happens
it's already happening
intel submitted the patches to GCC today
Current Intel hardware mitigations do not cover TAA and current Cascade Lake CPUs remain vulnerable. TAA can allow leaking of data across processes, privilege boundaries and Hyper Threading. With Hyper Threading disabled, TAA can still leak data from protected domains.
yikes imagine leaking data even when HT is off
also the next time you cherrypick benchmarks
>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 ~