Comment 6 for bug 1820798

It looks like the stack-clash detection is getting tripped up on optimization:

ubuntu@stensal-disco-server-amd64:~$ gcc -O2 -o stack-clash -fstack-clash-protection stack-clash.c
ubuntu@stensal-disco-server-amd64:~$ ./hardening-check ./stack-clash
./stack-clash:
 Position Independent Executable: yes
 Stack protected: yes
 Fortify Source functions: no, only unprotected functions found!
 Read-only relocations: yes
 Immediate binding: yes
 Stack clash protection: no, not found!
ubuntu@stensal-disco-server-amd64:~$ gcc -o stack-clash -fstack-clash-protection stack-clash.c
ubuntu@stensal-disco-server-amd64:~$ ./hardening-check ./stack-clash
./stack-clash:
 Position Independent Executable: yes
 Stack protected: yes
 Fortify Source functions: no, only unprotected functions found!
 Read-only relocations: yes
 Immediate binding: yes
 Stack clash protection: yes