• 2 Posts
  • 34 Comments
Joined 17 days ago
cake
Cake day: June 13th, 2024

help-circle










  • The only part of a JIT compiler I don’t understand how it works is the part that swaps in compiled routines during interpretation. That’s the point I’m unsure of how to write in Rust because it seems like it would require very custom control flow. It might be that you can handle this by storing your compiled instructions somewhere using the C calling convention and then having Rust call your compiled function like a C function.

    In essence, what you have is a Rust program that has to produce machine code (easy!), store it somewhere in RAM (also easy, I think), and then somehow call it (how???). The final part seems like the difficult one since passing execution into arbitrary memory they just wrote is just the sort of thing programs aren’t normally supposed to do.










  • Amanda@aggregatet.orgtoTechnology@lemmy.worldWhy we don't have 128-bit CPUs
    link
    fedilink
    English
    arrow-up
    36
    arrow-down
    1
    ·
    8 days ago

    The comments on this one really surprised me. I thought the kinds of people who hang out on XDA-developers were developers. I assumed that developers had a much better understanding of computer architecture than the people commenting (who of course may not be representative of all readers).

    I also get the idea that the writer is being vague not to simplify but because they genuinely don’t know the details, which feels even worse.