fuhsnn

10 ms·

91.
by fuhsnn 1y ago
Wasm intrinsics look neat as a higher-level fixed size SIMD abstraction. I wonder how good the compilers can do if using them for AOT targets with libraries like simd-everywhere. string.h is missing strstr(), there's an algorithm of si
92.
by fuhsnn 2y ago
We might get multi-line macros in C2y standard: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3524.txt
93.
by fuhsnn 2y ago
> How about some __int128 literals There are _BitInt literals (wb and uwb), look adequate https://godbolt.org/z/xjEEM5Pa4 despite clang's "is a C23 extension" noise.
94.
by fuhsnn 2y ago
That was the response to your "what someone has told you is a binary" argument, if you learnt the basics of programming, you will know it's just a hexdump away to verify a binary, there's no one else in the room to tell
95.
by fuhsnn 2y ago
> Anyway, so your means of forming trust in a compiler faithfully compiling code, is to trust a decompiler to faithfully generate human readable source code No, it is to fully audit the binary of a compiler itself, if you don't trus
96.
by fuhsnn 2y ago
Not a programmer, are you? Programmers can fully investigate the compiled binary without anyone even has a chance to lie to them. If a team don't have the ability to audit the decompilation of a 10k LOC C compiler at least once, I doub
97.
by fuhsnn 2y ago
You bootstrap the compiler with itself and audit whether the compiler binary is exactly the same semantics as its source. >Full source bootstrapping is our only way out of the trusting trust problem No, that is just deferring the trust t
98.
by fuhsnn 2y ago
The fosslinux/live-bootstrap project is more about bootstrapping from minimal binary seed than auditability, for the latter case I'd argue that having a readable C cross-compiler is clearer than going through multiple steps involv
99.
by fuhsnn 2y ago
Thanks, looking forward to it!
100.
by fuhsnn 2y ago
>I’ve been modifying the the MIR c2mir JIT compiler to extend the c11 compiler to support simple classes, boxed strings(immutable, nun-nullable) with AOT support Is the project public? Really interested in the AOT support, I've alwa
101.
by fuhsnn 2y ago
Zig and Odin compiler may implicitly pass variables by references[1][2], creating hidden aliasing, that's one thing unacceptable for me coming from C, I haven't read about C3 doing this, hopefully it doesn't and not planned i
102.
by fuhsnn 2y ago
If you are taking notes, add `-fzero-init-padding-bits=all` to the list, without this flag, GCC 15 onwards will not zero-initialize a full union if you wrote pre-C23 style ={0} and the largest member is not the first one. `-ftrivial-auto-va
103.
by fuhsnn 2y ago
>These posts are not going to describe how to implement a cycle-accurate YM2612 emulator For those interested, https://github.com/nukeykt/Nuked-OPN2 reverse-engineered YM3438 from die-shot.
104.
by fuhsnn 2y ago
I just started learning to setup containers and found nspawn a total convenience, just create ./usr, throw some static-linked binaries to ./bin and systemd-nspawn -D would handle the rest including network pass-through.
105.
by fuhsnn 2y ago
>the proposal is tailored so that other than simple syntax support no new semantics need to be implemented within GCC Not just GCC, but you're right it's tailored, to the same "unwinding" queue that C++ destructor, st
106.
by fuhsnn 2y ago
You can play with defer in Linux/VM with slimcc[1] today! It only diverges from the TS in keyword being _Defer, as well as several goto constraint violations not detected, bright side is you can witness why they are constraint violatio
107.
by fuhsnn 2y ago
>if you think this is a fix I would count it as doing maintenance work for the upstream, kudos for doing this!
108.
by fuhsnn 2y ago
For the cases in linked doc, does adding -std=gnu17 to packages not suffice? I would consider the union initializer change (require adding -fzero-init-padding-bits=unions for old behavior) much more hidden and dangerous, which is not direct
109.
by fuhsnn 2y ago
The proposed C defer is scope-based unlike Go. So in the spirit of OP article, you can basically hand roll not only C++ destructor as defer {obj.dtor()} but also Rust Drop as defer {obj.notmoved() ? Drop()}
110.
by fuhsnn 2y ago
It reads like they are not using cross compilation and instead running compilers inside QEMU? It's surprising to me, as Chimera being an LLVM + musl distro shouldn't be impossible to cross-compile most userland packages.
111.
by fuhsnn 2y ago
Probably the current state that GCC for Aarch64 and RISC-V simply don't offer individual register constraints like x86.
112.
by fuhsnn 2y ago
>You own any right, title, or interest that may exist >We hereby assign to You all our right, title, and interest, if any >You are solely responsible for Outputs and Your use of Outputs I love how it clearly laid out the scenario t
113.
by fuhsnn 2y ago
I think it's mostly the lack of comparable research other than the Skylake-X one by Travis Downs. I too would like to see how Zen 4 behaves in the situation with its double-pumping.
114.
by fuhsnn 2y ago
>{0} initializer in C or C++ for unions no longer guarantees clearing of the whole union (except for static storage duration initialization), it just initializes the first union member to zero. I posted the same link last month to highli
115.
by fuhsnn 2y ago
I believe their system clang support it with -femulated-tls.
116.
by fuhsnn 2y ago
It does look serious, and is able to parse one simple case I got at hand that openwatcom and orangec failed, thanks for bringing it up.
117.
by fuhsnn 2y ago
The new "__VA_TAIL__" proposal for C2Y [1] will make these sorts of tricks much more manageable. I love it and implemented it right away in slimcc. [1] https://www.open-std.org/jtc1/sc22/wg14/www&#x2
118.
by fuhsnn 2y ago
>Those hints, carefully inserted by serious systems engineers, were often terrible! So much so that removing all of them increased the performance of the kernel. So glad I'm not alone, every time I tried to optimize hot loops with t
119.
by fuhsnn 2y ago
HN is weird, even GCC changelog could be flagged: https://news.ycombinator.com/item?id=42882343
120.
by fuhsnn 2y ago
I've never seen a mid-sized C codebase that annotate "restrict", "nonnull" pointers and "pure", "const" functions so thoroughly, very interesting, would be an important case study if I ever get a

More ›