News for hackers. Stuff that matters.
Re:Intel Skylake/Kaby Lake processors: broken hyper-threading by pshc on Sunday June 25, 2017 @12:17PM (#14630721)
I wonder if there's a CPU out there that doesn't have bugs.
Re:Intel Skylake/Kaby Lake processors: broken hyper-threading by userbinator on Sunday June 25, 2017 @12:36PM (#14630822)
It depends on how exactly you define a bug, but something like a 6502 or Z80, which has essentially all the errata well-documented since it has existed for so long, might qualify.
Re:Intel Skylake/Kaby Lake processors: broken hyper-threading by DamonHD on Sunday June 25, 2017 @03:06PM (#14631580)
Z80 implementations for one had a whole slew of undocumented instructions, allegedly because they were buggy in some way.
Re:Intel Skylake/Kaby Lake processors: broken hyper-threading by protomyth on Monday June 26, 2017 @07:33AM (#14635913)
The VIPER was built to be fully proven, but there was come debate on methodology.
Re:Intel Skylake/Kaby Lake processors: broken hyper-threading by autokad on Sunday June 25, 2017 @01:11PM (#14631011)
stop playing lawyer ball. i'm talking about the bugs that require turning off core functionality (such as hyperthreading) and/or that lead to system halts / corrupted data.

yes it happens, but software bugs happen every day where as if your system blue screened every day you know dang well you'd be on the phone with the hardware vendor for a refund / new system.

Re:Intel Skylake/Kaby Lake processors: broken hyper-threading by coldtea on Sunday June 25, 2017 @01:31PM (#14631120)
>yes it happens, but software bugs happen every day where as if your system blue screened every day you know dang well you'd be on the phone with the hardware vendor for a refund / new system.

Well, since hundreds of millions of people use Skylake/Kaby Lake CPUs for 2 years now, and only now we learn about this, obviously this is not of the "system blue screens every day" variety but a very rare bug.

Re:Intel Skylake/Kaby Lake processors: broken hyper-threading by sqldba on Monday June 26, 2017 @12:35AM (#14634121)
> obviously this is not of the "system blue screens every day" variety but a very rare bug

Not to be anal but we can't know this.