On Thu, Jul 13, 2017 at 04:32:02PM -0500, Segher Boessenkool wrote:
> I don't think it should be inside -fstack-check at all. Sure, the
> mechanisms implementing it overlap a bit (more on some targets, less
> on others), but how will a user ask for clash protection _and_ for
> stack checking?
Are we willing to implement that? What would we do in that case?
Probe in each function we emit both the current page that
-fstack-check=clash would probe and a page or how many below that how
-fstack-check=specific or generic would probe?
Even if yes, we can still use -fstack-check=clash,specific
for that (similarly to how we support -fsanitize=shift,unreachable).
But it is still a stack check kind.
Jakub
