4 ms·
There are reason why one would want to implement a RISC CPU over x86-64. Atleast as a small team. Another problem is that many application today assume the pres
by freemint 5y ago
There are reason why one would want to implement a RISC CPU over x86-64. Atleast as a small team. Another problem is that many application today assume the presence of atleast SSE if not AVX2 which have been around for longer then or almost a decade. A patent expired CPU will always have to play unless the architecture they clone was stopped being developed much (as SuperH was which J-Core based it's design on).
- sprash 5y agoAMD64 contains everything up to SSE2. AVX2 only exists since 2015. I doubt many applications require it.
- ColonelPhantom 5y agoI think most of today's software runs on any AMD64 CPU. That said, this is changing. GCC and LLVM developers have introduced aliases "x86_64-v2" through "x86_64-v4", with the non-existent "v1" being the base spec as defined by the Athlon 64/Opteron. v2 adds for example SSE4.2 and SSSE3, present since Intel Nehalem (first-generation Core i7 etc). I think other families support v2 since Intel Silvermont (Atom), AMD Bulldozer (FX), and AMD Jaguar (AMD E-series). I think one of the bigger losses would be AMD Phenom/Phenom II. I think Red Hat wants to require x86_64-v2 starting with RHEL9. Arch Linux seems to also have considered it, but seemingly has since decided to support both v1 and v3, to provide both a bigger speed boost and better compatibility with old PC's.