It's standard on Windows. In fact, LLVM properly implements stack probes for Windows since it's part of the ABI. Yet not anywhere else.
-
-
Replying to @CopperheadOS
Rust, a supposedly memory safe language, still lacks stack safety after they removed the working stack overflow checks in function preludes.
2 replies 3 retweets 9 likes -
Replying to @CopperheadOS
https://github.com/rust-lang/rust/issues/16012 … is not fixed with no sign of progress. It was obvious that this was going to happen when it was originally done.
2 replies 1 retweet 6 likes -
Replying to @CopperheadOS
CopperheadOS Retweeted Saul Procterm
https://twitter.com/pozdnychev/status/876826223850270720 … is an embarrassment for GCC / Clang / *nix. Gaping hole known about for years and properly addressed by Windows.
CopperheadOS added,
1 reply 6 retweets 20 likes -
Replying to @CopperheadOS
It looks worst for Rust where stack safety was implemented but was prematurely removed to get a 1-3% performance win without doing the work.
1 reply 1 retweet 7 likes -
Replying to @CopperheadOS
Rust used to use segmented stacks and then moved to simply aborting on stack exhaustion via the same overflow checks in function preludes.
1 reply 0 retweets 7 likes -
Replying to @CopperheadOS
Happen to be the one that initially pushed to kill seg stacks and use probes but in no way intended / expected premature removal of checks.
1 reply 0 retweets 1 like -
Replying to @CopperheadOS
CopperheadOS Retweeted CopperheadOS
Even Windows XP doesn't have this issue. Some time travel: https://twitter.com/CopperheadOS/status/659824199050108928 …. See you all in 2018 when this still hasn't been fixed.
CopperheadOS added,
1 reply 0 retweets 6 likes -
Replying to @CopperheadOS
The Linux kernel uses stack frame size warnings so it mostly avoids this problem but it does have some uses of C99 variable length arrays...
3 replies 0 retweets 4 likes -
Replying to @CopperheadOS
I think most of the "variable" lengths are actually crypto function properties and related stuff
2 replies 0 retweets 0 likes
I vaguely recall manually going through all the VLA uses at some point and not discovering any unbounded allocations
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.