HackerTrans
TopNewTrendsCommentsPastAskShowJobs

kjeetgill

no profile record

Submissions

InfiniBand, RoCE, and All That

fergusfinn.com
4 points·by kjeetgill·23 days ago·0 comments

Super Zsnes: GPU Powered SNES Emulation

youtube.com
4 points·by kjeetgill·3 months ago·0 comments

Stride and prejudice: How a 32-bit overflow corrupted a CUDA kernel

ai21.com
2 points·by kjeetgill·3 months ago·0 comments

Desperately Seeking Squircles (2018)

figma.com
18 points·by kjeetgill·6 months ago·8 comments

Making a game engine based on dynamic signed distance fields

youtube.com
1 points·by kjeetgill·6 months ago·0 comments

comments

kjeetgill
·7 months ago·discuss
Depending on what your working on, it's actually super nice to know very clearly what lives on the stack vs the heap for performance and compactness reasons. Basically anything that didn't come from malloc or a function calling malloc lives on the stack and doesn't live past the function it was allocated in.

And these days, if you're bothering with C you probably care about these things. Accidentally promoting from the stack to the heap would be annoying.
kjeetgill
·2 years ago·discuss
Unfortunate typo. I assume you meant ethnically not ethically.
kjeetgill
·3 years ago·discuss
I haven't heard about this, can you elaborate on this?