jesse__

17 ms·

241.
by jesse__ 1y ago
Oh my god, same. This literally catches bugs with a smoking gun in their hand in a way that's completely impossible with printf. I'd upvote this 100 times if I could.
242.
by jesse__ 1y ago
Location: BC Canada Remote only : 10 years remote, 12 years experience Technologies : C, C++, SIMD, OpenGL, WebGL, WASM, JS, TS Interests : compilers, language runtimes, 2D & 3D graphics, performance -------- Hello, my name is Jesse. I&
243.
by jesse__ 1y ago
This is exactly the issue, and unordered_map exemplifies it perfectly. On paper, unordered_map sounds great. It lists all the admirable properties you would theoretically want in a hashtable. Then in practice when you go to implement it
244.
by jesse__ 1y ago
10/10 comment
245.
by jesse__ 1y ago
Would have loved to see performance comparisons along the way, instead of just the small squashed graph at the end. Nice article otherwise :)
246.
by jesse__ 1y ago
Location: BC Canada Remote only : 10 years remote, 12 years experience Technologies : C, C++, SIMD, OpenGL, WebGL, WASM, JS, TS Interests : compilers, language runtimes, 2D & 3D graphics, performance -------- Hello, my name is Jesse. I&
247.
by jesse__ 1y ago
Minor nitpick, 32bit max value is ~4 billion, not 4 million
248.
by jesse__ 1y ago
> Always, Always Require a Compilation Step [...] as opposed to, say, writing code as it will be run I have a hard time believing that writing vanilla JS is superior to using a compiled language in any but very simple cases. Seems like
249.
by jesse__ 1y ago
Nothing specifically for the moment. I've toyed with the idea of having an option for smooth terrain, but it's not important for the game I'm currently making.
250.
by jesse__ 1y ago
I've been working on a 3D voxel-based game engine for like 10 years in my spare time. The most recent big job has been to port the world gen and editor to the GPU, which has had some pretty cute knock-on effects. The most interesting i
251.
by jesse__ 1y ago
Nice. Looks like it handles quite a bit. I just supported a single div op, which was enough for my needs. https://github.com/scallyw4g/bonsai_stdlib/blob/71fadd0f1fce...
252.
by jesse__ 1y ago
Generally agree, especially with the sentiment that it's a huge PITA maintaining something like this across multiple compilers & platforms. Out of curiosity, does highway implement integer divide?
253.
by jesse__ 1y ago
lol, alright dude. Good luck with C++26
254.
by jesse__ 1y ago
That sounds really great. I'm away from the office for the week but when I'm back I'll take a closer look and maybe squeeze some more juice out of it :)
255.
by jesse__ 1y ago
Hey, thanks for the comment! I did actually take a look at the aes instructions and came to the conclusion that they are in fact faster than the hash I used, but I think I'd decided I would have to swizzle the data in a way that was a
256.
by jesse__ 1y ago
There are 4 parts. Spoiler: I went to AVX and beat the state of the art by 1.8x Also, doing it on the GPU is worth it, if you do large batches.
257.
by jesse__ 1y ago
There's a lot to discuss. First off, a number of statements are nonsense. Take, for example > you shouldn't be writing SIMD instructions directly unless you're writing a SIMD library or an optimizing compiler. Why would w
258.
by jesse__ 1y ago
I disagree pretty strongly with most of what you said, but I'd be very interested in seeing a Highway example and looking at the differences. Take a look through the comments, I left a link to the test bench I made, which contains all
259.
by jesse__ 1y ago
I kinda did post results at the end of part 4 .. I beat the SOTA by 1.8x There's a benchmark utility here: https://github.com/scallyw4g/bonsai_noise_bench Fastnoise2 is a high quality library. Can't speak to
260.
by jesse__ 1y ago
I haven't looked at opensimplex. I will when I get around to doing a simplex implementation. And thanks for the kind words!
261.
by jesse__ 1y ago
I just called _rdtsc() before and after the noise gen once every iteration, and pushed the sample onto a fixed size buffer .. after some N iterations (4k maybe, can't remember) of samples, computed min/max/avg. There's a
262.
by jesse__ 1y ago
I only build the project this is embedded in with clang, so that's the only compiler I tested.
263.
by jesse__ 1y ago
Clang -O2 .. -O3 didn't seem to make any appreciable difference. Re. the auto-vectorization, I really don't know. I didn't even read the assembly the compiler generated until at least halfway through the process. Generally I
264.
by jesse__ 1y ago
Author here, AMA :)
265.
by jesse__ 1y ago
I recently finished a 4 part series about vectorizing perlin noise.. from the very basics up to beating the state-of-the-art by 1.8x https://scallywag.software/vim/blog/simd-perlin-noise-i
266.
by jesse__ 1y ago
It's extremely easy to beat the compiler by dropping down to SIMD intrinsics. I recently wrote a 4 part .. guide? .. https://scallywag.software/vim/blog/simd-perlin-noise-i
267.
by jesse__ 1y ago
1. Choosing a shitty architecture to absorb the downside of low quality tools seems like a bad decision, but I guess that's just where the industry's at right now. 2. AFAIK Go can both compile and load DLLs now. A language that d
268.
by jesse__ 1y ago
> I’ve definitely wondered about this. Like why does the language-understanding standard have to be a server specifically? I don't think it does. I think it's a bad architectural decision that web bros thought sounded cute. &g
269.
by jesse__ 1y ago
IMO, many of these are marginal or nonce gains for the huge cost of introducing a network call in the middle of your program. 1. There's nothing stopping you from shoving the library code onto a thread. For something like this request
270.
by jesse__ 1y ago
It's concerning to me that the LSP idea is .. a thing. Casey Muratori observed years ago that it's just a way worse way of doing libraries. Like, you're introducing HTTP where there could just be a function call into a DLL&

More ›