You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Is nobody attacking AMD, or is there some difference in design philosophy that has spared them from this wave of chip attacks?
This isn't a chip attack, it's a stupid design bug. That said, there *is* a difference in design philosophy. Intel has chosen performance over any kind of design sanity / safety, every time, it seems as a systematic rule. AMD hasn't.
So while both AMD and Intel have been equally hit by the general idea of speculation-based leaks in userland code (nothing the CPU can do about that), Intel has also had a huge pile of massively privilege-crossing speculation leaks that AMD hasn't.
Because the Intel philosophy seems to have been "ignore security/sanity until the instruction retires", so all kinds of batshit insane stuff happens in speculation on Intel CPUs (like bypassing guest VM page tables or loading bad or privileged data) which doesn't on AMD.
I recall reading the Intel Core 2 processor programming manuals which clearly described the task switch process as well as the required pipeline flush. But just like with 386, everyone ignored Intel’s design documents and skipped the slow but safe stuff.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
