5 ms·
In absence of better data, we have to compare compiler output.
by snvzz 7mo ago
In absence of better data, we have to compare compiler output.
- userbinator 7mo agoHere is your "better data": https://web.eece.maine.edu/~vweaver/papers/iccd09/ll_document.pdf https://web.eece.maine.edu/~vweaver/papers/iccd09/ll_documen...
- sitharus 7mo agoIf I recall my lectures, which were 20odd years ago now. CISC ISAs were historically designed for humans writing assembly so they have single instructions with complex behaviour and consequently very high instruction density. RISC was designed to eliminate the complex decoding logic and replace it with compiler logic, using higher throughput from the much reduced decoding logic (or in some cases no decoding at all) to offset the increased number of instructions. Also the transistors that were used for decoding could be used for additional ALUs to increase parallelism. So RISC by its nature is more verbose. Does the tradeoff still make sense? Depends who you ask.
- snvzz 7mo agoFrom 2017, it predates RISC-V first ratified spec. Currently, RISC-V holds the crown of code density in both 64 and 32 bit. On 32bit, thumb2 is a little behind. On 64bit, x86-64 is not even close, and ARMv8/v9 are even worse.
- userbinator 7mo agoYou've shown absolutely zero evidence. "Maybe if I keep repeating it, it'll be true."
- snvzz 7mo agoI am sure you are capable of running a compiler and/or running `size` on Ubuntu binaries.