Live data from Hacker News

Rust SIMD on the GPU

vectorware.com

51–60 of 132 posts

Re: Rust SIMD on the GPU

#54

Love the pendantic mode setting on the website

I don't get what's the value of it not being enabled by default what does the toggle get us, really? Maybe I don't understand web design and it makes it harder to read for some, I am dyslexic and never had any issues.

Re: Rust SIMD on the GPU

#55
post #7

Earlier quoted context omitted.

We never mention anything about superiority nor compare with other languages or programming models. This post is about making existing Rust CPU code work on the GPU.

[flagged]

Those aren't lines you are reading. Those are your hallucinations.

At worst, the post reads like a propaganda for VectorWare, but, overall, it reads more like their insights on the matter.

Re: Rust SIMD on the GPU

#57

I love how ever example of portable SIMD isn't portable. They specifies a constant SIMD width so it's non-portable. Well, not performance portable, but why are we using SIMD again?

It should really be read/advertised as "portabler SIMD". It beats hoping the compiler autovectorizes everything well forever or writing architecture specific code manually again but is going to compromise on average performance vs platform specific SIMD.

Re: Rust SIMD on the GPU

#59
post #4

Author here, AMA.

If you have to express your computation using an "array programming DSL" with things like scan and gather anyways - why not opt to use torch/tensorflow/jax or anything else that targets MLIR? An example of writing a relu using an embedded array DSL is really not helping your case either - that's exactly the problem that these other solutions mentioned above are successfully solving for the past ~15y (starting with theano etc). Not sure what this brings to the table - doing that AoT instead of at runtime?

Re: Rust SIMD on the GPU

#60
post #54

Love the pendantic mode setting on the website

I don't get what's the value of it not being enabled by default what does the toggle get us, really? Maybe I don't understand web design and it makes it harder to read for some, I am dyslexic and never had any issues.

It's just a way for us to add minutia and details that most don't care / need to know about. There are three audiences we try to make the posts accessible for: Rust people who don't know about GPUs, GPU people who don't know about Rust, and non-Rust non-GPU people. The toggle lets knowledgable readers go "wait, what about..." and hopefully the toggle answers it.
Post reply on HN