cc1: warning: ‘-fstack-check=’ and ‘-fstack-clash_protection’ are mutually exclusive. Disabling ‘-fstack-check=’
(there's a typo in gcc's message, the underscore should be a dash)
Is -fstack-clash-protection safer than -fstack-check? From the man page it sounds like that's the case, but i'm not sure i understand what i'm reading. My lay person understanding is; stack-check verifies that memory is not accessed past what should be the end of the stack (based on the memory range allocated for the stack?). stack-clash-protection accesses each location iteratively so that it can be checked for the guard page (end of stack marker) before going further.