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 ~

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

https://www.servethehome.com/intel-performance-strategy-team-publishing-intentionally-misleading-benchmarks/

https://www.techquila.co.in/amd-epyc-rome-servers-beat-intel-xeon-in-netflix-video-bandwidth-by-2x/

gaming wont be hit by CPU performance since it's more GPU now

quality: low

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