µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime
1–10 of 65 posts
Re: µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime
#2This is an optional runtime used to improve error reporting with the Clang sanitizer:
Re: µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime
#3>I've decided to write the whole µUBSan runtime as a single self-contained .c soure-code file, as it makes it easier for it to be reused by every interested party.
I don't really get why people do this. Linking is one of the easiest and most broadly supported features of C environments on every platform.
Re: µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime
#4Darned Good Stuff!
Is the runtime API shared between both GCC and LLVM/Clang?
Re: µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime
#5>I've decided to write the whole µUBSan runtime as a single self-contained .c soure-code file, as it makes it easier for it to be reused by every interested party. I don't really get why people do this. Linking is one of the easiest and most broadly supported features of C environments on every platform.
[deleted]
Re: µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime
#6>I've decided to write the whole µUBSan runtime as a single self-contained .c soure-code file, as it makes it easier for it to be reused by every interested party. I don't really get why people do this. Linking is one of the easiest and most broadly supported features of C environments on every platform.
As someone with a very casual knowledge of C, I am thankful when people do this. All you need to do is #include "x" and it just works, having to configure the compiler and linking can be painful. Experienced developers might see it as a disadvatage for some reason, but it is a godsend for beginners.
Re: µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime
#7>I've decided to write the whole µUBSan runtime as a single self-contained .c soure-code file, as it makes it easier for it to be reused by every interested party. I don't really get why people do this. Linking is one of the easiest and most broadly supported features of C environments on every platform.
As someone with a very casual knowledge of C, I am thankful when people do this. All you need to do is #include "x" and it just works, having to configure the compiler and linking can be painful. Experienced developers might see it as a disadvatage for some reason, but it is a godsend for beginners.
I think it just trains beginners on how to do things wrong. The basics of linking two pieces of code together aren't terribly complicated and are essential C knowledge.
Re: µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime
#8>I've decided to write the whole µUBSan runtime as a single self-contained .c soure-code file, as it makes it easier for it to be reused by every interested party. I don't really get why people do this. Linking is one of the easiest and most broadly supported features of C environments on every platform.
It makes it easier to relink against a different standard library like musl. Or for cross compilation. The fewer files to deal with the fewer places I have to look for issues in porting.
Re: µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime
#9>I've decided to write the whole µUBSan runtime as a single self-contained .c soure-code file, as it makes it easier for it to be reused by every interested party. I don't really get why people do this. Linking is one of the easiest and most broadly supported features of C environments on every platform.
> Linking is one of the easiest and most broadly supported features of C environments on every platform.
No, it's absolutely not easier. And the more you deviate from amd64 linux and gcc, the harder it gets.
Re: µUBSan: clean-room reimplementation of the Undefined Behavior Sanitizer runtime
#10>I've decided to write the whole µUBSan runtime as a single self-contained .c soure-code file, as it makes it easier for it to be reused by every interested party. I don't really get why people do this. Linking is one of the easiest and most broadly supported features of C environments on every platform.
It makes it easier to relink against a different standard library like musl. Or for cross compilation. The fewer files to deal with the fewer places I have to look for issues in porting.
I mean, you're already going to have to recompile stuff for either of those cases. Once you're compiling things, compiling several files isn't much harder.