meadori
Joined 11 years ago
Joined 11 years ago
1. The maintainer of llgo is a Google employee (and a very talented LLVM engineer).
2. I don't imagine there would be tremendous differences in the strategies used to generate LLVM IR between the tools. ISTM, if there are deficiencies in llgo, then it would be better to fix them rather than creating a whole new tool. > The exercises accompanying this book focus on teaching cryptography by breaking inferior systems.Sometimes I feel like my life would be much easier if I could just focus on one or a small few things :-)
It is not the best when it comes to explaining things in an intuitive manner. It is a great reference book with lots of algorithms and proofs.
In recent years I have been drawn more towards Levitin's "Introduction to the Design and Analysis of Algorithms".
Anyone else have similar feelings about "Introduction to Algorithms"?
http://pyvideo.org/video/3465/exploring-is-never-boring-unde...
While it is focused on CPython, most of the techniques are applicable elsewhere. It also mentions a great article by Peter Seibel (http://www.gigamonkeys.com/code-reading/) that discusses why we don't often read code in the same way we would literature.
Essentially, as the complexity of software has grown people have been forced to take a more experimental approach to understand software even though it was created by other people.
What exactly do you mean by this? Direct object code emission?
> the emulator is easier than the compiler, by a lot
Yeah, definite +1 there. For most simple machines it really is not much more than a loop with a switch on the opcode where the cases update the CPU state.