News for hackers. Stuff that matters.
Re:Unicorn: a lightweight multi-platform, multi-architecture... by amelius on Sunday August 02, 2015 @06:45AM (#9990337)
> Implemented in pure C language

It seems to me that enormous performance gains could be attained by JIT-compiling the assembly instructions to native assembly instructions.

Re:Unicorn: a lightweight multi-platform, multi-architecture... by asb on Sunday August 02, 2015 @07:55AM (#9990467)
Re:Unicorn: a lightweight multi-platform, multi-architecture... by pygy_ on Sunday August 02, 2015 @08:44AM (#9990561)
Is it still written in plain C like the former dyngen?
Re:Unicorn: a lightweight multi-platform, multi-architecture... by sgk284 on Sunday August 02, 2015 @06:53AM (#9990359)
How would that interact with code that modifies itself?
Re:Unicorn: a lightweight multi-platform, multi-architecture... by AlexAltea on Sunday August 02, 2015 @07:07AM (#9990393)
If the emulator detects a memory write to one of the already recompiled blocks it can invalidate the results of the previous translation. If branch occurs to that block or to a new area in memory where new instructions were emitted, it can translate that part and cache the results. With a JIT binary translator this is no big deal. However, AOT translation of self-modifying code would not work.