Computer architecture
This new edition of 'Computer Architecture' has been updated throughout to address the historic shift from single-core to multi-core processors.
Stats for nerds
59recommend
110mentions
94people
2008–2026years
64% recommend35% neutral1% critical
Mentions per year
What Hacker News says
- >but it's a lot more instructions so it won't be used in practice.
It will be used when it needs to be handled. e.g. where elsewhere, an exception would actually handle it. Which is seldom the case.
More instructions doesn't mean slower, either. Superscalar machines have a hard time keeping themselves busy, and this is an easily parallelizable task.
>The designers of RISC-V included the bare minimum needed to compile C, everything else was deemed irrelevant.
Refer to "Computer Architecture: A Quantitative Approach" by by John L. Hennessy and David A. Patterson, for the actual methodology followed.
- Computer architecture a quantitative approach by Patterson and hennessy
It’s the real life exchange rate for algorithms and data structures. Basically understanding your infrastructure and its performance characteristics will help you design simpler ( and therefore better )systems
- From a hardware perspective, juggling is better without flags and without unnecessary addressing modes.
Neither are concepts RISC-V invented, but rather, adopted. Ideas that have been plenty tested out there, and proven beneficial.
Large body of evidence trumps intuition and guesswork. Most of this is documented in the spec itself and/or in:
Computer Architecture: A Quantitative Approach (John L. Hennessy, David A. Patterson)
- I would split the books into two categories: those that improve the way you structure your code and deliver a software solution, and those that improve your technical understanding of the software platform and the computer you're using.
The first are books like Pragmatic Programmer, Mythical Man Month, Code Complete, Design Patterns, talks by Alan Kay on software systems and OOP, even Game Engine Architecture etc. A lot of the content there is distilled experience which is much faster to learn from a book than gain the hard way on the job.
The other books are practical deep dives. Here I would recommend a variety of books like Inside the Machine by Stokes, Computer Architecture by Hennessy, 21st Century C by Klemens, Crafting Interpreters by Nystrom, Compilers by Aho, Effective Java, Nature of Code by Shiffman, Ray Tracing Challenge by Buck, Hands on Hacking by Hickey, and others, depending on your interest and area of focus.
- From your description of your current level, reading Patterson's "Computer Architecture: a Quantitative Approach" would be a next good step.
Related
Computer organization and design
50 recommend · 101
Computing
1 recommend · 2
Computer system architecture
6 recommend · 7
Digital Design and Computer Architecture
26 recommend · 43
Compilers, principles, techniques, and tools
195 recommend · 958
Computer Networks
50 recommend · 110
