Andreas Kling (@awesomekling) on X

X (formerly Twitter) ·

1 min read Original article ↗

@awesomekling

Had a strange performance regression from a seemingly innocuous code change, and GPT-5.6 tracked it down to a microcode workaround for an Intel CPU bug. The workaround can make conditional jumps that straddle a 32-byte boundary much slower, so programs have to be laid out around it. Tried building with -mbranches-within-32B-boundaries and wouldn't you know it, we're fast again! The future is so fucking cool! intel.com/content/www/us…

Mitigation Strategies for JCC Microcode

From intel.com

12:56 PM · Jul 22, 202619.1KViews