GPU Offload in Rust: Portable, Safe, and Fast

(arxiv.org)

52 points | by linggen 2 hours ago

5 comments

  • jasonjmcghee 21 minutes ago
    > the rust-gpu project has to emulate pointers[8], which we consider a blocking issue for most HPC benchmarks.

    Why is it a blocking issue?

    I feel like this is very aligned with the goals of rust-gpu.

  • rfgplk 12 minutes ago
    Fascinating how many people still overcomplicate offloading to GPUs.
  • Thomashuet 43 minutes ago
    That's promising but did they publish any code? I can't find anything in the abstract.
  • jheriko 7 minutes ago
    [dead]
  • iberator 1 hour ago
    [flagged]
    • aabhay 1 hour ago
      Genuinely curious what these constant changes are. In fact I don’t feel they’re moving fast enough to give us improvements to core.
      • frollogaston 52 minutes ago
        It was changing quickly in the earliest releases, about 10 years ago. Like one day I pulled our repo and there was new "?" syntax, but that was a feature I'd been wanting anyway.

        Edit: Oh, async/await was a bigger and more recent one, 2019. I've heard that this wasn't an easy decision for them but was kinda needed.

        • aabhay 37 minutes ago
          A few years in between releases with a sane versioning system seems fine to me. If you don’t want new features don’t build with that new toolchain.

          It’s not javascript where you need to support all possible browsers.

          • frollogaston 26 minutes ago
            Teams will disagree over what toolchain to use, and you will read others' code, so this doesn't dodge the issue. Otherwise there'd be no complaint about C++. I don't think Rust is bloated though, every feature has a very good reason.
    • jjice 1 hour ago
      That's an opinion. One you're very welcome to hold, but it's not universal by any means. Lots of people enjoy rust.