3 ms·
The issue i have with Sedgwick, cormen et al is they ignore hardware. Is Knuth really better? How is the cache heirachy different in MMIX as compared MIX?
by harry8 9y ago
The issue i have with Sedgwick, cormen et al is they ignore hardware. Is Knuth really better?
How is the cache heirachy different in MMIX as compared MIX?
- Jtsummers 9y agoWhat hardware should they base their book on? Would it be universally applicable? Should they drop down to assembly level (as Knuth has) or stick to some higher level language? Their choice of using a pseudocode allows the algorithms they discuss to be accurately and completely specified, while leaving the implementations up to specific platform (hardware and language) developers and users.
- deleted 9y ago[deleted]
- hackermailman 9y agoVolume 4a there's a dozen or so mentions and examples of writing cache-friendly code. CS:APP 3/e is another book that gives general advice for writing cache friendly code. In fact CS:APP the chapters you can read side by side with TAOCP series: floating point, arithmetic operations, bit shifting, optimizations, boolean logic ect are in both books with TAOCP going much more into detail of course. I used the TAOCP chapter on bitwise ops in 4a to finish my CS:APP datalab assignment that was giving me problems.