Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The MBA is a good candidate for Tiger Lake.

Intel-Client-Mobility-CPU-Roadmap-2020-10nm-14nm-Ice-Lake-Comet-Lake-Tiger-Lake-Rocket-Lake-1030x560.png



Possibly. If the above is to be believed (it already looks like at least their Comet Lake-H prediction is wrong on both scheduling and offering 10 cores), Comet Lake-Y is coming roughly the same time.

I wonder if either of those two (assuming Comet Lake-Y even exists) will be offered in 7W, and if that's what Apple is waiting for. (Ice Lake-Y is 9W!)
 
Renoir is a bit bigger than Tiger Lake which is quite bigger than Ice Lake.
 
OK lets go through your errors!
RISC & CISC still has a large bearing on how the OS and apps run on a given CPU. Modern Intel CPU's are CISC at the ASM layer before the instructions are decoded and dispatched by the microcode which at the lower layers has some RISC elements. The instructions are all CISC.

OS-X & MacOS contains a lot of Objective-C, kernel is in C as well as Embedded C++, as well as assembler code for low level file system for performance. Windows 7 and newer was written in C++, kernel is in C.

ARM64 has no bearing here as Apple has their own chip design and instruction set (most of it is not disclosed). If Apple used a plain jane ARM64 APU then you might have something but Apple is not likely to do that.

No iOS was ported from OS-X when it was on the PowerPC CPU. iPod was still very different it was never a full OS!

When Apple ported OS-X from PowerPC to Intel it did a full rewrite of the Darwin micro kernel and the rest of the the code to work on CISC processors.

When Apple ported over iOS it needed to trim back a lot of the bulk removing lots of the code as it just wouldn't fit in the limited RAM and storage the first iPhone had (iPhone OS is the original name of iOS).

I don't under stand your referencing an emulator as that has no bearing in this.
[automerge]1578971934[/automerge]


Some of us old farts remember the first generation of OS-X which ran on IBM's PowerPC (RISC based). NeXTSTEP was the source of Apples OS-X kernel Darwin and most of the supporting elements.

When IBM/Motorola couldn't match the performance on what Intel was doing Apple jumped to Intel CISIC CPU's Core Duo and then on to Core 2 Duo and then onto the i3/5/7 CPU's.

The i CPU's where a big change for Intel as the microcode leveraged some RISC technology which get people confused!

Adding in ARM CPU's into the mix then gets into which flavor of ARM! Arm's ARM or Apples ARM which are similar but still very different from each other!

C/C++ code are portable if you care about portability from start.

If almost everything is written in high level language then why RISC/CISC matters? They are not touching assembly code. LLVM clang will do the work for you and there's nothing secret for A series instructions as you can right now de-assembly the iOS app binary you compiled from Xcode to see the instructions. All of them are ARMv8/ARMv8.2 instructions. The compiler clang(LLVM) is even open source since beginning.

It's totally insane to believe a CPU instruction is secret when people have to build app to run on it.

Mac OS X was multi arch since beginning and port to Intel is a proof of that. CISC/RISC never matters.

Emulator is mentioned here as Xcode 11 introduced a new library format names"xcframework". This is specially designed to hold multiple binaries in one package for library distribution and hinting Apple is working on supporting developer for multi arch. It's quite clear you are not a iOS/Mac developer. As the "errors" you pointed out are actually your own errors.

BTW: You really think people are porting OS using only assembly code? There's no such thing called "port OS X from PowerPC". PowerPC and Intel runs almost same code just compiled differently.

PowerPC assembly is dramatically different from ARM even they are both considered "RISC" style.
There's no way you can port a system without the source code.
 
Last edited:
OK lets go through your errors!

This is… an ironic way to start that post, but let's just address one point in particular:

ARM64 has no bearing here as Apple has their own chip design and instruction set (most of it is not disclosed). If Apple used a plain jane ARM64 APU then you might have something but Apple is not likely to do that.

Apple Ax implement AArch64. Apple has some proprietary extensions, but obviously they are disclosed; after all, you need to be able to write code (or have your compiler generate code) that takes advantage of them, or they would be rather useless.

By and large, an Apple Ax chip is just an implementation of ARMv8.3‑A. The magic isn't in the instruction set; it's in Apple's design.

Adding in ARM CPU's into the mix then gets into which flavor of ARM! Arm's ARM or Apples ARM which are similar but still very different from each other!

"Apple's ARM" is almost entirely… ARM.
 
I remember the days when Intel bragged about hitting 10Gz. Thermal limits stopped them in their tracks. They then went with multiple cores to provide upgraded performance with turbo boost and whatever to stay in the lead. I believe x86 has nearly reached its limit. No matter what their nanometer process. ARM is the future and I know many will disagree. It will be interesting to see what happens in the coming decade.
 
I remember the days when Intel bragged about hitting 10Gz. Thermal limits stopped them in their tracks. They then went with multiple cores to provide upgraded performance with turbo boost and whatever to stay in the lead. I believe x86 has nearly reached its limit. No matter what their nanometer process. ARM is the future and I know many will disagree. It will be interesting to see what happens in the coming decade.

Apple might decrease the CPU orders from Intel if it can't offer a better price than Ryzen 4000 Mobile APU.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.