6 ms·
Reductio ad absurdum – writing a single-instruction C compiler [video]
- icebraining 9y agoThe actual compiler has been discussed in the past on HN [1][2], but I thought the talk was an well structured explanation of the process, and more interesting than the compiler itself. [1] https://news.ycombinator.com/item?id=12372242 https://news.ycombinator.com/item?id=12372242 [2] https://news.ycombinator.com/item?id=10021259 https://news.ycombinator.com/item?id=10021259
- Kapura 9y agoIt's theoretically interesting up until the point where he starts eliminating registers and moving things to memory addresses. Main memory is significantly slower to access than in-processor registers. Granted, if you are taking the mov-only computation engine to it's logical conclusion (as Domas does) you may be able to speed up the hardware architecture to compensate for these losses, but is there anything of actionable value to gain from such a process? (i did really enjoy the talk, fwiw)
- progval 9y ago> you may be able to speed up the hardware architecture to compensate for these losses It reminds me of the concept of Scratchpad memory: https://en.wikipedia.org/wiki/Scratchpad_memory https://en.wikipedia.org/wiki/Scratchpad_memory However, the main issue is with branches. As all code is executed all the time, the execution time is exponential in the number of basic blocks in the control-flow graph C program.
- qubex 9y agoOISC (One Instruction Set Computing) is a well-known concept in theoretical computer science. It is not considered an avenue for for performance computing. https://en.wikipedia.org/wiki/One_instruction_set_computer?wprov=sfti1 https://en.wikipedia.org/wiki/One_instruction_set_computer?w...
- adrianN 9y agoI wonder whether mov-oriented programming would a useful obfuscation technique for malware authors. I'd assume that typical disassemblers are not very helpful.
- posterboy 9y agoone talk I remember said as much. If i remember correctly, repeated obfuscation via self modifying code can increase code size dramatically, though a correlation to time complexity was not shown (and I don't remember how the code modified).
- juskrey 9y agoObfuscation uses a lot of techniques including this. Redundancy also allows to create polymorphic code, that is which creates variable copies of itself.
- viraptor 9y agoYes/no. Yes, because it's (slightly) harder to see what's executed. No, because AVs will soon get a rule like: basic block full of MOVs - flag it immediately. Some AVs even flag UPX packed executables by default, so it wouldn't be unexpected.
- missjellyfish 9y agoThere is the demovfuscator, which de-obfuscates movfuscated programs reasonably well. This work was actually done by friends of mine; see their talk here: https://recon.cx/2016/talks/"Movfuscator-Be-Gone.html https://recon.cx/2016/talks/"Movfuscator-Be-Gone.html
- MaxBarraclough 9y agoInteresting, thanks for the link! Was just about to ask if such a project exists. I wonder if there are other OISC architectures that are harder to 'decompile'.
- teh_klev 9y agoAt around 34:30 in the talk he discusses this briefly, with the conclusion that you'd signature the data and also continue to monitor API calls etc. It wouldn't be such a big deal.
- igravious 9y agoMore Reductio ad singulum than Reductio ad absurdum :)
- utopcell 9y agoIf anything, this video showcases the importance of doing proper bibliographic research before working on a new problem. SISC (single instruction set computer) or OISC (One Instruction Set Computer) have been in Hennessy and Patterson for dozens of years.
- describrion 9y agoExcept, that wasn't at all the point of this presentation...