Skip to content
Better HN
Top
Best
Ask
Show
New
Jobs
Search
⌘K
0 points
kevin_thibedeau
7y ago
0 comments
Save
Share
> We were unable to reproduce this behavior on non-Intel CPUs and consider it likely that this is an implementation issue affecting only Intel CPUs.
The attacks are being attempted. AMD just didn't screw up as badly.
0 comments
1 comments · 1 top-level
top
newest
oldest
robotresearcher
7y ago
Trying Intel attacks on AMD just in case is cheap and easy, and in this case fruitless. It doesn’t shed any light on how much effort is being put into finding AMD’s own specific screw ups.
j
/
k
navigate · click thread line to collapse