> - No stack overflow check in release mode. -fstack-check in GCC guarantees that the guard page will be hit (as long as there is one), assuming no undefined b

> - No stack overflow check in release mode. -fstack-check in GCC guarantees that the guard page will be hit (as long as there is one), assuming no undefined behaviour like buffer overflows. It has a negligible cost and should really be enabled by default. It only has to add a one byte write per uninitialized page on the stack, and a less efficient dynamic alloca due to probes.