Stack Exchange
open access
CC BY-SA
Why would anyone want CISC?
In our computer systems lecture we were introduced to the MIPS processor. It was (re)developed over the course of the term and has in fact been quite easy to understand. It uses a RISC design, that is its elementary commands are regularly encoded and there are only few of them in order to keep the wires simple. It was mentioned that CISC follows a different philosophy. I looked briefly at the x86 instruction set and was shocked. I can not image how anyone would want to build a processor that uses so complex a command set! So I figure there have to be good arguments why large portions of the processor market use CISC architectures. What are they?
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- Service Function Chaining (SFC) Architecture#399253
- Characterizing the I/O Behavior of HPC Applications through Modeling and Simulation#780942
- Characterizing the I/O Behavior of HPC Applications through Modeling and Simulation#779567
- Automated Template-free Synthesis of Instruction-Centric Leakage Contracts for Black-Box CPUs#373321
- Arcalís: Accelerating Remote Procedure Calls Using a Líghtweight Near-Cache Solution#986201
Record · ID 796594
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive