fuhsnn

10 ms·

121.
by fuhsnn 2y ago
It's about the author's language named Apple[1], took a few seconds since Apple Array System unfortunately sounds like some MacOS framework. For people prefer C-like syntax, there is ispc[2], which supports x86 AVX and ARM Neon pr
122.
by fuhsnn 2y ago
>Phi just loads the value out of its shadow variable and assigns it to its implicit variable. Isn't this similar to block arguments? These shadow variables would have been block parameters, just unordered and maybe not explicitly co
123.
by fuhsnn 2y ago
>I'd still argue that the third optimization would be incorrect here That's my take as well, to apply it more defensively, any writes cannot be proven in-bounds should be considered clobbering q's state.
124.
by fuhsnn 2y ago
With "typeof" standardized in C23 it kinda does the job: int(* fnptr_name)(int param) becomes typeof(int(int param))* fnptr_name There is a recent proposal to update standard headers to this style: https://www.open-std.
125.
by fuhsnn 2y ago
Reminds me of Windows 95 era interactive games for kids.
126.
How to implement C23 embed in GCC 15(developers.redhat.com)
1 points by fuhsnn 2y ago|0 comments
127.
by fuhsnn 2y ago
>Seamless C++ interop More detail would be appreciated, I'm not aware of any non-transpiling language that actually support full C++ RTTI/exceptions interop.
128.
by fuhsnn 2y ago
Do they cover anything Sapphire Rapids Xeon's don't? I thought they share the same arch (Golden Cove).
129.
by fuhsnn 2y ago
There is no shame in simple codegen if it is correct and unsurprising!
130.
by fuhsnn 2y ago
>So one of the main problems you run into is that your elegant solution only works about 60-80% of the time. The rest of the time, you end up falling back onto near-unmaintainable, horribly inelegant kludges that end up having to exist T
131.
by fuhsnn 2y ago
Personal experience: I stopped at a point where brute-forcing started to feel "unwelcomed", I think it was this one: https://martin-ueding.de/posts/project-euler-solution-66-dio...
132.
by fuhsnn 2y ago
>They are brittle and a maintenance nightmare I happened to be reading DMC source this week, those hydrate/dehydrate stuff really is everywhere (which I assume is solely used for precompiled headers?)
133.
by fuhsnn 2y ago
That's from the OP blog, the intention of those macros is to generate uniquely named local lambda. Cleaner version is like: https://github.com/llvm/llvm-project/issues/100869#issue-243...
134.
by fuhsnn 2y ago
Including Linux kernel https://github.com/torvalds/linux/blob/master/include/linux/...
135.
by fuhsnn 2y ago
The C++ lambda version can be a foot gun: https://godbolt.org/z/Wd66GcrdG , if the return value is a struct, NRVO (named return value optimization) may be applied and the lambda will be called in different order. As for
136.
by fuhsnn 2y ago
I wonder what's the author's view on Forth, seems like the role of the bytecode VM here might be interchangeable with a Forth implementation.
137.
by fuhsnn 2y ago
One of my earliest surprises is: input-only and output-only may be mapped to the same register, and explicitly mapping one of them will not prevent this: https://godbolt.org/z/bo3r749Ge
138.
by fuhsnn 2y ago
>That's what LLMs are for - idiom translation. You can't trust them to do it right, though. Optimizing C compilers also happened to be good at idiom recognition, and we can probably trust them a little more. The OP paper does m
139.
by fuhsnn 2y ago
>feel fresh yet familiar This probably applies to most mainstream entertainment.
140.
by fuhsnn 2y ago
All jazz artists started as insignificant band members before they found their voice.
141.
by fuhsnn 2y ago
Geometry of Music by Dmitri Tymoczko is a fun book of visualizing chromatic music theory with geometry models, some of it also covered in author's papers https://dmitri.mycpanel.princeton.edu/publications.html
142.
by fuhsnn 2y ago
>[4]: https://git.sr.ht/~vdupras/duskos/tree/master/item/fs/doc/co... I've been looking for C compiler implementation in Forth, this is great work!
143.
by fuhsnn 2y ago
>making function pointers into integers as that makes passing them between heterogenous architectures This is interesting, though function pointers are long expected to be address on binary, C-brained people like me would probably adapt
144.
by fuhsnn 2y ago
I wonder how GPU is going to access an unknown size NULL terminated string in system RAM, the strchr() source looks like normal C++. In my minimal Vulkan GPGPU experience the data need to be bound to VkDeviceMemory to be accessible through
145.
by fuhsnn 2y ago
Thanks for clarifying!
146.
by fuhsnn 2y ago
Looks like this is implemented with LLVM's builtin matrix type, also available as a Clang extension: https://clang.llvm.org/docs/MatrixTypes.html
147.
by fuhsnn 2y ago
I tested with tcc, cparser and my own slimcc, the benchmark showed multiple process with htop, so there are some dynamic cpu scaling randomness going on. I saw larger run-to-run differences with the same binary, than with comparing cherry-p
148.
by fuhsnn 2y ago
It's not so bad as long as the gears are taken good care of, if this isn't a thing we'll find them defunct in a dumpster yard. There are still positives about having a vintage collector scene, like USB floppy emulator kits, L
149.
by fuhsnn 2y ago
Copy or move for C++ is just choosing which constructor/assignment overload to call. I believe it's possible to make C++ move-by-default if one go through the trouble of overloading every class you use with custom move procedures.
150.
by fuhsnn 2y ago
>It's also for this reason that DX7 only has membrane buttons, and no knobs or sliders. It didn't need them. I wouldn't romanticize it as anything other than cost-cutting, later flagship models got sliders.

More ›