Jan Ph. H.

This sounds pretty much like valgrind except that valgrind has in-build Kernel ressource annotations, whereas this annotation is user-based (possibly inside libstd). Open questions: - 1. usage: Are these resource...

> I have run tests on Linux and created 1000 threads (that did something, not just looping) and found that each used about 32-64k for the stack in real physical...

After quite long discussion with @EleanorNB and some afterthought I get to the following possible simplifications: A more simple overapproximation may lead to very significant inaccuracies, but for completeness the...

AdaCore has GNATstack as tool. However, the description in the link is lacking some aforementioned assumptions and/or is unprecise on what type of arithmetic properties with resulting call graph information...

Related is https://interrupt.memfault.com/blog/measuring-stack-usage as state of art description: - 1. `clang/gcc -c -fstack-usage stack-usage-example.c` ```c // stack-usage-example.c #include int foo_2(int c) { int array[4]; array[1] = c; array[3] = c*...

I would be in favor of a comptime-only growable slice, which only exists in a certain compilation mode and can be accessed with `expextCompileError` based on comptime-formatted input. Mixing fatal...

If we can spawn processes, then we can parse the output message like implemented in #15991.

The report for C lang suggest implementation-defined (lol, not portable) definitions https://resources.sei.cmu.edu/asset_files/TechnicalNote/2007_004_001_14846.pdf Though, as usual for C-stuff, report is underspecified as it does not elaborate on "performance overhead" vs "flexibility"...

> The novel idea here is to allow an arbitrary amount of overflow to occur by deferring the error checking until absolutely necessary Does the blog mention Interval arithmetic and...

> perhaps std deviation should be involved? 1. To be statistically correct, you would have first to do sufficient retries to estimate, if the standard deviation is the correct guess....