aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/valgrind/valgrind
AgeCommit message (Collapse)Author
2015-07-07valgrind: build with altivec only if it supportedKai Kang
Signed-off-by: Ting Liu <ting.liu@freescale.com> Signed-off-by: Armin Kuster <akuster808@gmail.com> Cherry-pick from branch dizzy. Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-07-07valgrind: fix typo in valgrind-remove-rpath.patchAndre McCurdy
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-05-23valgrind: remove arm tests that don't compileDave Lerner
[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 <dave.lerner@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-03-20valgrind: enable building on 4.x kernelMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-02-17valgrind: add glibc-2.21 to glibc.patchMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-05valgrind: Upgrade to 3.10.0Saul Wold
Rebase existing patches Add patch to fix rpath issue with ptest Signed-off-by: Saul Wold <sgw@linux.intel.com>
2014-10-10valgrind: Enforce 30 seconds limit for each testTudor Florea
Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-09-10valgrind: backport enabling for glibc 2.20Ross Burton
Now that we're running glibc 2.20 not 2.19, backport the configure.ac fixes from upstream. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-08-28valgrind/oprofile/systemd: no bashism in run-ptestRobert Yang
There is no bashism in the scripts, so use /bin/sh, and add /bin/sh interpreter for systemd's run-ptest. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-04-25Upstream-Status CleanupsSaul Wold
Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-20valgrind: integration of regression tests to ptestDave Lerner
Modifies valgrind's regression test framework to be compatible with the yocto PTEST framework as follows: * existing recipe valgrind*bb adds new methods: do_compile_ptest and do_install_ptest. * new file run-ptest adds the wrapper interface to the valgrind regression test script vg_regtest. * existing valgrind regression test script 'vg_regtest' changes to report the status of the valgrind component tests in the format that PTEST expects, instead of the valgrind formats, but only when vg_regtest is invoked with an optional --yocto-ptest argument * four new patches disable building tests that don't compile with the yocto compiler and default options. See the patches for details. Signed-off-by: Dave Lerner <dave.lerner@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2014-02-18valgrind: Add glibc 2.19 awarenessKhem Raj
It wont compile otherwise and fail with errors e.g. Valgrind requires glibc version 2.2 - 2.17 ... Signed-off-by: Khem Raj <raj.khem@gmail.com>
2013-12-21valgrind: upgrade to 3.9.0Cristiana Voicu
Changed patches directory to "valgrind"; Removed 4 patches because they were merged upstream; Updated 2 patches because now it has configure.ac instead of .in; Changed license md5 for 2 files because of a small change for copyright year Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2010-11-18valgrind: Upgraded to version 3.6.0Dongxiao Xu
Remove valgrind_3.5.0-svn_r11264.patch.bz2 which replaces version 3.5.0 to r11264. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2010-09-02valgrind: fix perl scriptsQing He
svn version of valgrind uses #! @PERL@ for several perl scripts. However, PERL in autoconf doesn't distinguish host perl and target perl, causing STAGING_DIR_NATIVE be written in the output scripts. This causes unrunnable scripts, and fails FILERDEPENDS mechanism (thus also do_rootfs_rpm). Uses /usr/bin/perl instead to fix it. Signed-off-by: Qing He <qing.he@intel.com>
2010-08-27Major layout change to the packages directoryRichard Purdie
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>