adityazero

3 ms·

1.
by adityazero 2mo ago
After all of the others were done with hacking? There was a point in time when it was giving some publicity, it is a bit late IMO.
2.
by adityazero 2mo ago
Rust/C/C++ all have a similar memory model, they were designed for a linear memory model. a `float ` does not carry the provenance (a float out of cudaMalloc or a malloc look the same to the rest of the program). This is the fund
3.
What a Pointer Forgets(vxlang.org)
3 points by adityazero 2mo ago|0 comments
4.
by adityazero 3mo ago
Really like that the barrier scopes and shuffle controls are type-level, that is a lot of footguns turned into compile errors. Once you lower to PTX, does any of that structure survive for ptxas to optimize on, or is it fully erased by then
5.
by adityazero 3mo ago
I just ask LLM to to give me a short tutorial on the thing i want to learn but i dont want to start from chapter-1, that is boring. so i upload my resume and say that make this tutorial based on the skillsets i already have. btw, this is a
6.
by adityazero 3mo ago
They are busy capturing market first, and I think that makes more sense. 'premature optimization etc.'
7.
by adityazero 3mo ago
There are market verticals where this makes a lot of sense. Embedded systems and IoT devices comes to mind. Even in data center space, I believe several layers can use fixed weights and remaining layers will compensate for the variations. P
8.
by adityazero 3mo ago
All of these would happily come back if Sundar left.
9.
by adityazero 3mo ago
> sundar, softly: “we can create a permission working group.” so true. i have attended meetings to decide on meeting topics for the next half.
10.
by adityazero 4mo ago
NVIDIA runs the other way. The instruction set is documented, but the `ptxas` compiler is not. And NVIDIA's documentation stops higher up than people assume: PTX is a virtual ISA, but SASS is published simply as a list of opcode names.