Periodic reminder: Don’t compile to C.
-
-
Replying to @pcwalton
Why? It's the only way to get native code without only supporting a few popular mainstream platforms.
2 replies 0 retweets 0 likes -
Replying to @RichFelker
Because of undefined behavior, bad error reporting, and never being able to implement proper GC, among other reasons.
4 replies 0 retweets 7 likes -
Replying to @pcwalton
If you generate C you can ensure it doesn't have any UB (assuming no interfacing with unsafe arbitrary C code), & can even do GC if you want (but GC is uhg).
1 reply 0 retweets 0 likes -
Replying to @RichFelker
It’s a big pain, though. Signed integer overflow, float<->int casting UB, etc. are all things people often don’t want in their language and makes the generated C really ugly. And you can’t do *good* GC. :) You need stack and register maps, which are impossible in C.
2 replies 0 retweets 2 likes -
Replying to @pcwalton @RichFelker
TBF LLVM has a lot of obnoxious UB around float <-> int operations, division, sqrt, etc. too
4 replies 0 retweets 2 likes -
Replying to @jckarter @RichFelker
Yep, and it’s caused us no end of pain in Rust. At least LLVM smoothes over *some* of C’s undefined behavior. It’d be even worse if we had to deal with all of C’s UB.
1 reply 0 retweets 1 like
It's no harder to generate F2I(x) than (int)x, where the former is a macro or inline function that handles OOB values correctly.
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.