David Bozier 3d50c64c92 [Stack Protection] Add diagnostic information for why stack protection was applied to a function ...

Stack Smash Protection is not completely free, so in hot code, the overhead it causes can cause performance issues. By adding diagnostic information for which functions have SSP and why, a user can quickly determine what they can do to stop SSP being applied to a specific hot function.

This change adds a remark that is reported by the stack protection code when an instruction or attribute is encountered that causes SSP to be applied.

Patch by: James Henderson

Differential Revision: https://reviews.llvm.org/D29023



git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@296483 91177308-0d34-0410-b5e6-96231b3b80d8

2017-02-28 16:02:37 +00:00

..

llvm

[Stack Protection] Add diagnostic information for why stack protection was applied to a function

2017-02-28 16:02:37 +00:00

llvm-c

[GVN] Initial check-in of a new global value numbering algorithm.

2016-12-22 16:03:48 +00:00