Stack problem

I think that the only part of the stack that Dan wants to R.I.P. is related to local arrays. I don't think that he cares about the stack consumption that is caused by keeping return addresses and passing subprogram arguments. If heavy recursion is not used, and subprogram calls are not deeply nested, this type of stack consumption is nothing to worry about.

Some compilers provide a switch for allocating local arrays on the heap if the required size is above a certain minimum, say 1 kB.

Mecej4 correctly summarized what my worries are. If processors and software are build with stacks in minds, then OK, let it stay, but the limit for stack in 64bit has to be literally the sky (OS and processor limits and the RAM size) and totally transparent for the programmer i.e. being automatically adjustable by the compiler. It's OK for the pro programmer who want's to mess with the stack get manual adjustments for stack but i have not seen anyone who got any worth his time advantages doing that. Guarantee that everyone who was forced to adjust the stack using this compiler had really bad experience with it.