—
Jest-in-Time compiler
musl's strlen() is a work of art except for the hopefully-harmless UB http://git.musl-libc.org/cgit/musl/tree/src/string/strlen.c …
@johnregehr don't forget musl's beauties such as this 64-bit atomic primitive which totally won't tear:
http://git.musl-libc.org/cgit/musl/tree/arch/arm/atomic.h#n247 …
-
-
@jfbastien I don't even understand -
@johnregehr@jfbastien Do you have more examples of questionable musl stuff? OpenWrt (many SOHO routers & IoT things) just switched to it... -
@BRIAN_____@johnregehr not at the moment, I'll send patches to@RichFelker once we start doing WebAssembly's libc using musl.
End of conversation
New conversation -
-
-
@jfbastien@johnregehr I want to `git blame` that a_crash() and scream at whoever wrote it, this person is unfit to write a libc -
@whitequark@jfbastien just recently I saw a similar function that didn't have any volatile qualifiers -
@johnregehr@jfbastien it's still UB when volatile-qualified, isn't it? -
@whitequark@jfbastien yes but it becomes very likely to behave as intended -
@johnregehr@whitequark@jfbastien if only there was a builtin that would cause gcc/clang to emit a trap. something like __builtin_trap. -
@johnregehr@whitequark this whole file is a horrifying collection of non-atomic implementations of things there are builtins for. what the?
End of conversation
New conversation -
-
-
@jfbastien@johnregehr a_{and,or}_64 are misnamed. They should be called atomic bitset/bitclear. Sorry!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.