aboutsummaryrefslogtreecommitdiff
path: root/src/core/CL/kernels/CLQuantizationLayerKernel.cpp
diff options
context:
space:
mode:
authorMoritz Pflanzer <moritz.pflanzer@arm.com>2017-09-14 14:33:20 +0100
committerAnthony Barbier <anthony.barbier@arm.com>2018-11-02 16:35:24 +0000
commit8b74c784e55b3c0747231b37d8f5dd8d4630d8d2 (patch)
treefb1315eefced49a044c05af90be316677d7b60ad /src/core/CL/kernels/CLQuantizationLayerKernel.cpp
parentbaf174e85ddb5399355281cd34d0f459d92124a7 (diff)
downloadComputeLibrary-8b74c784e55b3c0747231b37d8f5dd8d4630d8d2.tar.gz
COMPMID-417: Add -fstack-protector-strong flag
The compiler seems to perform some "illegal" optimisations regarding the stack pointer which cause valgrind to report invalid writes. (Or it could be a compiler bug). Compiling with -fstack-protector-strong generates "correct" code and thus allows to use valgrind. Change-Id: I841dc839b5edb49f6f27acc1b3904671294476fc Reviewed-on: http://mpd-gerrit.cambridge.arm.com/87719 Reviewed-by: Georgios Pinitas <georgios.pinitas@arm.com> Tested-by: Kaizen <jeremy.johnson+kaizengerrit@arm.com>
Diffstat (limited to 'src/core/CL/kernels/CLQuantizationLayerKernel.cpp')
0 files changed, 0 insertions, 0 deletions