4 ms·

So will this be affecting most Macbook Pros of the past few years? If so, there's a way to disable hyper-threading, but you need Xcode (Instruments). Open Ins

• rayiner 9y ago
  No. Even though Skylake came out in 2015, Apple used an older CPU (Haswell) until the October 2016 MacBook Pros.
  • reaperhulk 9y ago
    They used Skylake in late 2016 MBPs and Kaby in the 2017 models.
    • isatty 9y ago
      I'm on a Kaby Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz I haven't seen any erratic crashes yet on code compiled by LLVM 8.1.0 on multiple projects (ROS, Qt5). I hope a microcode fix is pushed by Apple on behalf of Intel soon.
      • pedrocr 9y ago
        Are you from the future? Isn't LLVM currently at 4.0 and going for 5.0 soon?
        • sclangdon 9y ago
          macOS comes with Apple's build of Clang, which has different versioning from "proper" Clang.
          • pedrocr 9y ago
            That's going to be mess when LLVM proper catches up to those version numbers...
        • isatty 9y ago
          It prefixes the version with Apple LLVM so I assume it is versioned differently.
• yborg 9y ago
  This is kind of like cutting off your leg because of a hangnail. I've been running a Skylake MBP for more than 6 months for compilation workloads and haven't seen a single processor hang. I'm much more annoyed by the completely unpredictable desktop assignment on monitors when hotplugging DisplayPort connections on multiple displays. This one bothers me every day.
  • richdougherty 9y ago
    > haven't seen a single processor hang If there was data corruption you might not notice.
  • ourcat 9y ago
    I agree. I've been fine myself. But if people feel the need to turn it off. ;)
  • codezero 9y ago
    That's weird re monitor issues. I've been impressed with how consistent mine are. What I see: Same monitor/monitors plugged into same ports produce consistent configs. I get a unique config per monitor/port.
• skm 9y ago
  If you're on a Mac, you can find the exact processor model number by opening Terminal.app and entering sysctl -n machdep.cpu.brand_string this will return something like Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz (Found on http://osxdaily.com/2011/07/15/get-cpu-info-via-command-line-in-mac-os-x/ http://osxdaily.com/2011/07/15/get-cpu-info-via-command-line... )
  • DamonHD 9y ago
    Exactly the same output for me. Assuming that's not the only hardwired output from that command, is your password also hunter2? B^>
• rsynnott 9y ago
  From one of the 2016 MacBook Pros: > machdep.cpu.model: 78 > ... > machdep.cpu.stepping: 3 > ... > machdep.cpu.microcode_version: 174 Can't find if 174 is the fixed version or not. So this is one of the models for which there exists a fix, as per the email.
  • deefcee 9y ago
    I'd also like to know if 78 is the fixed version.