The @musllibc UB-purge continues. https://git.musl-libc.org/cgit/musl/commit/?id=4d0a82170a25464c39522d7190b9fe302045ddb2 … and previous few commits.
-
Show this thread
-
The only "intentional UB" I'm aware of remaining is (aligned) over-read potentially past end-of-array in string ops. There is no GNU C construct to annotate and make this legal so I'm not sure what to do with it.
2 replies 0 retweets 4 likesShow this thread -
Replying to @RichFelker
Get the committee to make it implementation defined
1 reply 0 retweets 1 like -
Replying to @stephentyrone
They don't even govern it because it can only happen with GNU-C-specific may_alias types. Really GCC and clang should probably specify this if it's supposed to work.
2 replies 0 retweets 1 like -
Replying to @RichFelker
Would be nice to be able to grab the aligned block containing the first byte. I don’t think you can compute that address without formal UB.
2 replies 0 retweets 0 likes
You compute it in the address model with uintptr_t, where it's implementation-defined not undefined. That part is fine. The problem is just whether the compiler extension defines the access to it or not.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.