Change Details

When `-fstack-clash-protection` is enabled and stack has to be realigned, some parts of redzone is written prior the probe, so probe might overwrite content already written in redzone. To avoid it, the implementation should skip redzone when probing. Safety is still guaranteed since write in redzone is considered to be free probe. This fixes https://bugs.llvm.org/show_bug.cgi?id=49903.

When `-fstack-clash-protection` is enabled and stack has to be realigned, some parts of redzone is written prior the probe, so probe might overwrite content already written in redzone. To avoid it, we have to make sure the first probe is at full probe size or is the last probe so that we can skip redzone. This fixes https://bugs.llvm.org/show_bug.cgi?id=49903.

When `-fstack-clash-protection` is enabled and stack has to be realigned, some parts of redzone is written prior the probe, so probe might overwrite content already written in redzone. To avoid it, the implementation should skip redzone when probing. Safety is still guaranteed since write in redzone is considered to be free probwe have to make sure the first probe is at full probe size or is the last probe so that we can skip redzone. This fixes https://bugs.llvm.org/show_bug.cgi?id=49903.