If your program is structured correctly, you can track the maximum possible stack size and eliminate the possibility I've done it for firmware - ThreadSky

About ThreadSky

alyssa.codes • 28 days ago

If your program is structured correctly, you can track the maximum possible stack size and eliminate the possibility

I've done it for firmware

Comments

pcwalton.bsky.social•27 days ago

How do you deal with higher order functions? Just forbid them?

jamesmunns.com•27 days ago

Usually you need to annotate or limit recursion and really any use of function pointers or other form of dynamic dispatch.

It's hard in the general case, pretty tractable for systems with specific scope.

jamesmunns.com•27 days ago

https://github.com/Dirbaio/cargo-call-stack is fun, if you haven't seen it before

pcwalton.bsky.social•27 days ago

Have you considered something like k-CFA for allowing some subset of higher-order functions?

jamesmunns.com•27 days ago

I've not personally ever tried to implement a stack analysis tool, and I know that cargo-call-stack can handle SOME level of function pointers/indirection already.

When I worked in safety critical industries (in C), max stack analysis was more required, but we also had a strict coding standard.

jamesmunns.com•27 days ago

If you know how to improve the max-stack analysis in some way, there are certainly embedded folks who would appreciate it!

alyssa.codes•27 days ago

We were able to get some limited dynamic dispatch working with cargo-call-stacks, but I don't recall the details

IIRC we banned higher order functions in the crates where we enforced full-binary no-panic

mcy.gay•27 days ago

we love tarjan's algorithm

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply