disas

4 ms·

1.
by disas 5y ago
I see, thanks for the explanation. That's a neat trick!
2.
by disas 5y ago
> Lineiform is just a wrapper function that takes a closure as input, and returns a closure as output. In the middle however, it will dynamically inline calls to other closures that the input might be doing, using dynamic recompilation t
3.
by disas 5y ago
<shrug> At this point we have reduced your blog post's message from "Look at this amazing new feature! It's so novel and unique! All other compiler developers are complete idiots!" to "Sometimes when I read as
4.
by disas 5y ago
For actual analysis as opposed to cutesy blog post demos I'd actually use vi test.s But if you insist on doing things the hard way on stdout, GCC has got you covered as well. Add -o - to the command line.
5.
by disas 5y ago
I find cc -S test.c fastest to type.
6.
by disas 5y ago
> the very first C compilers... <checks calendar> 40 years ago Ah. Checking the calendar is not sufficient, one should also be able of doing correct arithmetic. 1972 was 50 years ago, not 40.
7.
by disas 5y ago
> I suggest you try it before dismissing it. It's changed the way I work, and has started changing the way others do, too. Try what? I know (and mentioned) two distinct ways of looking at the assembly code produced by my C compiler.
8.
by disas 5y ago
> But to build a compiler, you need to be able to see the output. A disassembler had to be built along with the compiler. Until very recently the dominant paradigm, at least for ahead-of-time compilers on Unix, was to emit textual assemb