]> code.ossystems Code Review - openembedded-core.git/commit
valgrind: let valgrind determine its own optimisation flags
authorAndre McCurdy <armccurdy@gmail.com>
Wed, 20 Jan 2016 02:47:49 +0000 (18:47 -0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 22 Jan 2016 23:42:37 +0000 (23:42 +0000)
commit1c8ed8dada8d3399bd825d6f34fc440ce793ec4e
treed095f0160feb9e64cca9534c8cfccb737a08124a
parent99d4d97f51b658d58a50789056b422e48df89ad9
valgrind: let valgrind determine its own optimisation flags

Valgrind likes to control its own optimisation flags. It generally
defaults to -O2 but uses -O0 for some specific test apps etc. Passing
our own flags (via CFLAGS) means we interfere with that.

Giving valgrind control of optimisation is hopefully an even better
solution than the previous one of forcing -O0 for all tests.

  http://git.openembedded.org/openembedded-core/commit/?h=master-next&id=98c4a3ffb8dca10739be600e8d6df7fb6aa4958f

Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb