This is a tracking issue for stabilizing stack smashing protection (i.e., -Z stack-protector). The was added in #84197 without a tracking issue. There is also no feature gate for it.

As part of the work on reviewing previously-added support for exploit mitigations to the Rust compiler (see https://hackmd.io/@rcvalle/H1epy5Xqn), @luismerino and I, and also @wesleywiser reviewed the stack smashing protection option (i.e., -Z stack-protector) implementation and it looked good for stabilization, so we'd like to propose stabilizing it.

Steps

TBD.

Unresolved Questions

Is there any concern or anything that the community would like to see implemented before its stabilization?

Implementation history

• add codegen option for using LLVM stack smash protection #84197
• Document stack smashing protection #93052
• LLVM 17 regression: tests/ui/abi/stack-protector.rs no longer actually attempts stack-smashing #109671
• Document stack-protector option #111722
• Add -Zstack-protector test for Windows targets #116037