I kind-of hope that this is true… for the pun alone.
What do you get when the following three things happen: the 40th anniversary of your introductory part, a product line that can contain your original products model number, and, of course, strong competition from your primary competitor? Maybe the Intel Core i7-8086K. Maybe an elaborate internet hoax.
Image Credit: DDAA117 via WCCFTech
The rumor claims that it will be a slightly up-clocked Core i7-8700K. It will retain the 6 cores, 12 threads, 12MB of L3 cache, and 95W TDP, but the core will be clocked at 4.0 GHz (up from 3.7) and it can boost on a single core up to maybe 5.1 GHz. Basically, if true, it sounds like Intel cherry-picked a few high-performing dies out of Coffee Lake-S and set them aside for a promotion around the Computex or E3 time frame.
From a consumer standpoint? The last anniversary processor was a great deal, so pricing will become the deciding factor. If you were interested in the Core i7-8700K, then you might want to wait and see whether this slight notch above is true.
Single core boost is old news
Single core boost is old news but yeah this is going to be a rebrand.
I would totally buy this
I would totally buy this today, and build a system I really don’t need around it. Just to be able to tell the 2 people i know that would get it, that it has an 8086 in it.
They would be missing a trick
They would be missing a trick if they don’t clock it at either 4.77Ghz (speed of 8086 in original IBM PC was 4.77MHz), or 5GHz (max speed of original 8086 was 5MHz).
And it shouldn’t be a K model, instead it should have a crystal on the substrate (preferably ceramic for old times sake) that you have to desolder and replace if you want to overclock it. If you are going to do an anniversary chip, do it properly.
“promotion around the
“promotion around the Computer or E3 time frame”
Is computer time frame the thing you cool to overclock a computer?
Lol whoops. :p
Apparently one
Lol whoops. :p
Apparently one of my coworkers fixed the typo. I meant Computex.
40 Years of x86 and maybe IBM
40 Years of x86 and maybe IBM should have gone with another ISA for their PC that started it all.
Maybe Apple will be going all in-house with their CPU needs but that’s a while off but the phone/tablet makers will never be x86, never ever! And that’s more to do with the supplier market freedom that’s built up around the ARM Holdings business model where Reference design CPUs can be licensed or only the ARMv8A ISA(In Apple’s/Samsung’s/some others Cases) can be licensed and a fully custom hardware solution created that is engineered to execute the ARMv8A ISA.
No CPU/SOC, or GPU, suppliers are calling the shots to any Phone/Tablet OEMs like in that x86/Discrete GPU market and the ARM ISA devices OEMs are loving their freedom to not have to give all of their margins to any CPU/SOC or GPU suppliers.
Apple’s A series processors are full custom hardware designs that are engineered to execute the ARMv8A ISA and the RISC ISA has better power usage metrics than any x86 CISC based designs. And that x86 “RISC” back-end nonsense still does not hold true as it still takes more transistors to implement a CISC ISA compared to a RISC ISA, more transistors more power used. The majority of any RISC ISA Machine code Instructions are translated in a 1 to 1 ratio from a Machine Language Instruction into a Micro-Op Instruction whereas the CISC instructions mostly translate into more than one Micro-Op instruction. So CISC CPUs are not going to have a power usage envelope suitable for smartphones and most mainstream tablets.
It’s too bad that some inside of AMD has pushed that custom K12 custom ARMv8A ISA running design(By Jim Keller/K12 team) onto the back burner. Samsung also has introduced a custom ARMv8A ISA running design the M3 Mongoose-3 core that’s every bit as wide order superscalar as Apple’s A series designs and the M3/Mongoose is even wider on the instruction issue and execution engine resources that Apples A series cores. For Apple’s custom SOCs however Apple saves even more power by offloading some processing tasks to more specialized processing units DSPs/AI processors and so does Qualcomm.
So Maybe AMD has better be careful and Keep those K12 blueprints handy and AMD better start looking at DSP/AI processing on any Lower power cores if AMD ever wants to try and field a tablet oriented or even chromebook oriented ARM based design that includes AMD’s graphics IP.
The OEM PC/laptop market is shrinking so x86 usage will be shrinking by default. AMD could make use of its K12 IP via its semi-custom CPU/SOC division and maybe some client will want a gaming oriented tablet design with lower power usage metrics in mind.
The x86 market is only going to continue to contract in the consumer markets relative to the ARM ISA designs and it was a fluke that allowed x86 to remain relevant for so long and IBM is the one that’s responsible for x86 being cross-licensed to others a move that so angered Intel’s opportunistic founders that do this day Intel can and will employ methods that will result in legal judgments that Intel just writes off as the cost of doing business.
The Phone Market will never be x86 based and that’s been a good thing for consumers and the RISC ISA custom ARM cores are getting pretty much as wide order superscalar as a desktop processor and look at the IBM Power8/Power9 RISC designs in those government supercomputers and Power is a RISC ISA just like The ARM ISA so Apple will have not problem beefing up its in-house custom cores for laptops in the 2020 later time frame.
Perfect. Let’s wait on the
Perfect. Let’s wait on the thermals, mobo compata and the main issue may be the pricing. I would suggest Intel is playing catchup at this point, my last was a 6600k but my 1700 really stomps it. Like, a lot.
Well, you know if Intel(s) are reading, nice birthday gift I’d hope. Shares and all though – bit of a shock on the pricing thing I’d scope.
Excellent reporting as always PC Per / Shrout Research | Team.
I’ll get it only if it’s
I’ll get it only if it’s confirmed the 8086K is not vulnerable to Meltdown.