Message from @Tervy
Discord ID: 644504759042310147
I wish phones were exciting again
<:soy:589104157248585749> Flip
ekkeekkeek thanks to those new(old) vulnerabilities :D INTEL disabled HLE (hardware lock elision) from all the CPUs :D
if you want to see how it can affect your jobs https://twitter.com/damageboy/status/1194751035136450560
the first time in the history of computing where the technology has gotten slower (not counting shitty development)
when highly optimised code takes 30% hit to the dick
it aint fun day for intel :D
unfortunately intel seems to still support my 10 year old xeon :|
bet core2quads (unpatched now) will be faster than my Lynnfields
Twitter link goes nowhere
ahh apparently <> adds shit to the end some reason
what in the fuck
now it works
you added a space in front of the link bruh
between < and the link
might be
well color me suprised
yes
mainly because AMD doesn't even have it so you have to be compiling for intel in the first place
yeah so any larger server systems who actualy need all juice they can get
what actualy do computing and heavy lifting :D
but indeed for normal users the HLE hit aint __that__ bad expect on probly some rare cases
HLE is about machine code
it's an instruction
yeah but all thing i know have had problems/used it have had something to do with C so i was just quessing
HLE adds two instruction prefixes
which through some black magic fuckery are backwards compatible
so they can remove HLE without breaking anything
since it'll just fall back
the performance loss that tweet is talking about is unrelated to HLE instructions itself
the microcode update changed something relating to how jump instructions are decoded
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)