| ??? 06/27/06 08:26 Read: times |
#119178 - Estimating stack usage Responding to: ???'s previous message |
Trapping stack overflow would be a really useful addition to any soft core or future '51 variant. I'd also love to see a stack 'high water mark', as estimating stack usage in a program of any complexity is not trivial. |
| Topic | Author | Date |
| best practice regarding SP | 01/01/70 00:00 | |
| an easier method | 01/01/70 00:00 | |
| the other way round | 01/01/70 00:00 | |
| as a general rule | 01/01/70 00:00 | |
| Good rule | 01/01/70 00:00 | |
| on stack and data | 01/01/70 00:00 | |
| Estimating stack usage | 01/01/70 00:00 | |
| The future is now | 01/01/70 00:00 | |
| I'd like it also as interrupt... | 01/01/70 00:00 | |
| where would you store the interrupt retu | 01/01/70 00:00 | |
| what return??? | 01/01/70 00:00 | |
| then don't call it an interrupt | 01/01/70 00:00 | |
| OK, call it... exception? | 01/01/70 00:00 | |
| Trap perhaps? | 01/01/70 00:00 | |
| trap! | 01/01/70 00:00 | |
| the root | 01/01/70 00:00 | |
| Fair point | 01/01/70 00:00 | |
| signaling | 01/01/70 00:00 | |
avost? | 01/01/70 00:00 |