The only good comparison is to judge a variety of real world programs compiled for each architecture, and run them.
I'm guessing that you don't realize that you are describing SPEC?
It's been around since the days when every workstation vendor had their own bespoke CPU design and it literally takes hours to run the full set of workloads.
From the same Anandtech article linked above:
> SPEC CPU 2017 is a series of standardized tests used to probe the overall performance between different systems, different architectures, different microarchitectures, and setups. The code has to be compiled, and then the results can be submitted to an online database for comparison. It covers a range of integer and floating point workloads, and can be very optimized for each CPU, so it is important to check how the benchmarks are being compiled and run.
More info:
> SPEC is the Standard Performance Evaluation Corporation, a non-profit organization founded in 1988 to establish standardized performance benchmarks that are objective, meaningful, clearly defined, and readily available. SPEC members include hardware and software vendors, universities, and researchers.
SPEC was founded on the realization that "An ounce of honest data is worth a pound of marketing hype".
additionally, the only updates they appear to have made in the last 5+ years involve optimizing the suite for Apple chips.
thus, it leaves out massive parts of modern computing, and the (many) additions to x86-64 that have been introduced since the 00s.
i'd encourage you to look into the advancements that have occurred in SIMD instructions since the olden days, and the way in which various programs, and compilers, are changed to take advantage of them
ARM is nice and all, but the benchmark you've linked appears to be some extremely outdated schlock that is peddled for $1000 a pop from a web page out of the history books. Really. Take a look through what the benchmarks on that page are actually using for tooling.
I'd consider the results valid if they were calculated using an up to date, and maintained, toolset, like that provided by openbenchmarking.org (the owner of which has been producing some excellent ARM64 vs Intel benchmarks on various workloads, particularly recently).
How do you theorize that generic C or C++ code that you compile using GCC has been "optimized for an Apple chip"?
Feankly, it's impossible to take any of this comment seriously.
Over time, RISC and CISC borrowed from each other: https://cs.stanford.edu/people/eroberts/courses/soco/project...