Pushing the limits of RISC-V emulation

(shuklaayu.sh)

23 points | by shuklaayush 7 days ago

1 comments

  • dmitrygr 2 hours ago
    At the end it is not emulation but static recompilation (which is, arguably, cooler)
    • throwaway27448 1 hour ago
      How do you differentiate the two? What is the benefit of such a distinction? Why not use eg threaded emulation vs recompiled emulation?
      • drunken_thor 54 minutes ago
        In my limited understanding, static recompiling is like JIT transpilation from one arch to another where emulation runs each instruction calling behaviour depending on the instruction. As for tradeoffs my knowledge is not wide enough to declare anything certain.
        • throwaway27448 26 minutes ago
          What is the distinction in your mind? Can recompiling not call each instruction? Can threaded interpretation not perform optimization?
      • dmitrygr 59 minutes ago
        Emulation visits instructions as they are executed. Static recompilation will (at translation time) visit instructions that can be discovered, even if they never run.

        eg:

           if (rand64() == 0x123456789abcdef0ull)
              baz = bar;
        
        an emulator will likely never visit that assignment. A static recompiler will translate it.
        • throwaway27448 56 minutes ago
          Hm. What is the utility of this distinction?

          Anyway, qemu certainly seems like it would fall under your definition of "emulator" despite obviously dynamically recompiling.

          • dmitrygr 27 minutes ago
            which is why i said "static recompiler" and not just "recompiler"

            distinction is that an emulator is much simpler, while a static recompiler is a lot more work and thus ~30% more cool

            • throwaway27448 26 minutes ago
              Ah. I admit I've only ever made dynamic recompilers