home.social

#l636 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #l636, aggregated by home.social.

  1. @SnoopJ and re. design, the important realization is that "decoder library" as a separate function, separate binary, anything like that, it's probably grossly bad for throughput! so yaxpeax-sm83 has this callback thing i have no idea how to generalize: github.com/iximeow/yaxpeax-sm8

    so this specializes with the cpu impl: github.com/iximeow/yaxgbc/blob so that there aren't separate decode/execute functions :D what was like 20 instructions to decode, 30 to do ABI glue + call/ret, 20 instructions to emulate, that all turned into like 15 instructions to decode and emulate most ops

  2. @SnoopJ and re. design, the important realization is that "decoder library" as a separate function, separate binary, anything like that, it's probably grossly bad for throughput! so yaxpeax-sm83 has this callback thing i have no idea how to generalize: github.com/iximeow/yaxpeax-sm8

    so this specializes with the cpu impl: github.com/iximeow/yaxgbc/blob so that there aren't separate decode/execute functions :D what was like 20 instructions to decode, 30 to do ABI glue + call/ret, 20 instructions to emulate, that all turned into like 15 instructions to decode and emulate most ops

  3. @SnoopJ and re. design, the important realization is that "decoder library" as a separate function, separate binary, anything like that, it's probably grossly bad for throughput! so yaxpeax-sm83 has this callback thing i have no idea how to generalize: github.com/iximeow/yaxpeax-sm8

    so this specializes with the cpu impl: github.com/iximeow/yaxgbc/blob so that there aren't separate decode/execute functions :D what was like 20 instructions to decode, 30 to do ABI glue + call/ret, 20 instructions to emulate, that all turned into like 15 instructions to decode and emulate most ops

  4. @SnoopJ and re. design, the important realization is that "decoder library" as a separate function, separate binary, anything like that, it's probably grossly bad for throughput! so yaxpeax-sm83 has this callback thing i have no idea how to generalize: github.com/iximeow/yaxpeax-sm8

    so this specializes with the cpu impl: github.com/iximeow/yaxgbc/blob so that there aren't separate decode/execute functions :D what was like 20 instructions to decode, 30 to do ABI glue + call/ret, 20 instructions to emulate, that all turned into like 15 instructions to decode and emulate most ops

  5. @SnoopJ and re. design, the important realization is that "decoder library" as a separate function, separate binary, anything like that, it's probably grossly bad for throughput! so yaxpeax-sm83 has this callback thing i have no idea how to generalize: github.com/iximeow/yaxpeax-sm8

    so this specializes with the cpu impl: github.com/iximeow/yaxgbc/blob so that there aren't separate decode/execute functions :D what was like 20 instructions to decode, 30 to do ABI glue + call/ret, 20 instructions to emulate, that all turned into like 15 instructions to decode and emulate most ops