I noticed from www-client/chromium-124.0.6367.118 build that it still use -fstack-protector. This should overwrite the -fstack-protector-strong option that we are using by default in hardened profile and default profile with gcc[ssp] I'm wondering if there a particular reason about why google still keeping -fstack-protector