2 ms·
While this is quite nifty, I don't see why people other than LLVM developers would be interested in the LLVM IR output. Isn't the final CPU real assembly more i
by secondcoming 6y ago
While this is quite nifty, I don't see why people other than LLVM developers would be interested in the LLVM IR output. Isn't the final CPU real assembly more informative?
- ChrisSD 6y agoIn a literal sense, the LLVM IR is more informative because it literally has more information attached to the instructions. This information gets lost when the machine code is produced. This information will be very useful to any compiler that uses LLVM as a back end, not just LLVM itself. Of course it may not be particularly useful to anyone else unless they're particularly interested in trying to diagnose why their code is being optimized in a certain way.
- DudeInBasement 6y agohttps://github.com/xoreaxeaxeax/movfuscator https://github.com/xoreaxeaxeax/movfuscator Only move instructions
- dahfizz 6y agoI also imagine the compiler developers population has a high overlap with the "neck beard" type c developer, unix person that would prefer not to use a web app as part of their development workflow. It turns out that there's already a really easy way of executing compiler output on your CPU without the use of JavaScript...
- diegoperini 6y agoI'm a hobbyist compiler developer who does dev on Atom, debug in repl.it and prototype in Coffescript to generate LLVM IR. The world is big!