openembedded-core.git/meta/recipes-devtools/valgrind, branch jethro

meta: Fix Upstream-Status statements

2015-09-12T21:59:01+00:00

Fix a variety of problems such as typos, bad punctuations, or incorrect
Upstream-Status values.

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

valgrind: enable rt_sigpending syscall on ppc64 linux

2015-09-02T22:46:08+00:00

When running one application under Valgrind on ppc64 arch, we got a
missing syscall error. Get upstream patch from valgrind website to
enable rt_sigpending syscall on ppc64 linux.

Signed-off-by: Li Zhou 
Signed-off-by: Richard Purdie

valgrind: build ptests without optimizations

2015-08-19T16:57:52+00:00

This commit changes the both CFLAGS and CXXFLAGS when building the
valgrind ptest binaries by appending -O0, forcing no optimizations
instead of the default -O2.  For qemux86-64, this change results in
FAIL/PASS ratio improvements from 149/394 to 58/485.

It is evident that the expected result files were generated from
regression tests binaries built without optimizations.

[ YOCTO #8063 ]

Signed-off-by: Dave Lerner 
Signed-off-by: Ross Burton

valgrind: Fix build with glibc 2.22

2015-08-16T08:23:21+00:00

Signed-off-by: Khem Raj 
Signed-off-by: Ross Burton

valgrind: build with altivec only if it supported

2015-07-07T22:57:11+00:00

Signed-off-by: Ting Liu 
Signed-off-by: Armin Kuster 

Cherry-pick from branch dizzy.

Signed-off-by: Kai Kang 
Signed-off-by: Ross Burton

valgrind: fix typo in valgrind-remove-rpath.patch

2015-07-07T12:32:59+00:00

Signed-off-by: Andre McCurdy 
Signed-off-by: Richard Purdie

valgrind: remove arm tests that don't compile

2015-05-23T07:10:13+00:00

[Yocto #7453]

Corrects the original commit for the patch that removed ARM ptest CFLAGS
settings. Since the flags could be set by a user, the flags should
be kept in place during compilation.  By keeping the original up-stream
CFLAGS for the tests, then additional tests successfully compile
for all tested ARM tunings.

However, there were still two tests listed below that did not compile
for any beaglebone tuning that is valid for valgrind. With the updated
patch, the set of excluded ARM ptests and their respective build
failures are:
  intdiv - fails for all beaglebone tunings with 2 errors:
  {standard input}:(40 or 41): Error: selected processor does not
       support Thumb mode `udiv r3,r9,r10'
  {standard input}:(72 or 73): Error: selected processor does not
       support Thumb mode `sdiv r3,r9,r10'

  vcvt_fixed_float_VFP - fails for all beaglebone tunings in one of
  two ways:
    with neon tuning (-mfpu=neon) fails with Internal Compiler Error
    without neon tuning fails with 3 errors:
    {standard input}:33: Error: selected FPU does not support
      instruction -- `vcvt.f32.s32 s15,s15,#1'
    {standard input}:58: Error: selected FPU does not support
      instruction -- `vcvt.f32.s32 s15,s15,#32'
    {standard input}:136: Error: selected FPU does not support
      instruction -- `vcvt.f32.u32 s15,s15,#1'

After applying this commit, the valgrind ARM ptests compile without
errors for tunings:
  armv7[t][hf][b][-neon] cortexa8[t][hf][-neon]
where the tuning [option] was successfully compiled, both with
and without the 'option', and in combination with all other options.

Signed-off-by: Dave Lerner 
Signed-off-by: Ross Burton

valgrind: add configure option to build only 32-bit or 64-bit components

2015-04-06T19:36:06+00:00

Building both 32-bit and 64-bit binaries in valgrind at a time would
lead to following QA issue as below,

(snip)
 ERROR: QA Issue: Architecture did not match (62 to 3) on ${WORKDIR}/valgrind/3.10.1-r0/packages-split/valgrind-dbg/usr/lib64/valgrind/.debug/vgpreload_exp-sgcheck-x86-linux.so
 ERROR: QA Issue: Architecture did not match (62 to 3) on ${WORKDIR}/valgrind/3.10.1-r0/packages-split/valgrind-dbg/usr/lib64/valgrind/.debug/getoff-x86-linux
 ERROR: QA Issue: Architecture did not match (62 to 3) on ${WORKDIR}/valgrind/3.10.1-r0/packages-split/valgrind-dbg/usr/lib64/valgrind/.debug/vgpreload_core-x86-linux.so
 ERROR: QA Issue: Architecture did not match (62 to 3) on ${WORKDIR}/valgrind/3.10.1-r0/packages-split/valgrind-dbg/usr/lib64/valgrind/.debug/vgpreload_memcheck-x86-linux.so
-- CUT --

hence perform only one type of build 32-bit or 64-bit, but not both.

Signed-off-by: Krishnanjanappa, Jagadeesh 
Signed-off-by: Richard Purdie

valgrind: enable build for MIPS

2015-03-24T17:52:39+00:00

Since 3.8.0, valgrind supports MIPS32. MIPS64 was added in 3.9.0.

Signed-off-by: Andreas Oberritter 
Signed-off-by: Richard Purdie

valgrind: enable building on 4.x kernel

2015-03-20T11:03:17+00:00

Signed-off-by: Martin Jansa 
Signed-off-by: Ross Burton