diff options
| author |   Ronan Le Martret <ronan.lemartret@iot.bzh> | 2018-08-22 13:43:05 +0000 |
|---|---|---|
| committer | ronan Le Martret <ronan.lemartret@iot.bzh> | 2018-08-23 10:06:31 +0000 |
| commit | 16d03b87304e2bcb01d97a560caf80ecd1d5afda (patch) | |
| tree | 9f63800d5f18bd86e34b2cdd1e9652c56cbffefa /meta-agl-profile-core/recipes-devtools/valgrind/valgrind/avoid-neon-for-targets-which-don-t-support-it.patch | |
| parent | 66d9349794b11b0bb557028e7aa084ea1246985a (diff) | |
Port the latest version of valgrind
Some issues appear with the current version of valgrind on aarch64.
(valgrind exits due to an unhandled instruction)
An update of valgrind solves this problem.
I guess other platform need a update on valgrind too, so this port is
not gen3 exclusive.
This port uses the yocto
recipes(poky:7e7ee662f5dea4d090293045f7498093322802cc):
* with some fix on the patch.
* remove patch already merged in valgrind git.
Bug-AGL: SPEC-1677
Change-Id: Ibf467bee03487252f24ef046b9fe4e4ff6d389da
Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>
Diffstat (limited to 'meta-agl-profile-core/recipes-devtools/valgrind/valgrind/avoid-neon-for-targets-which-don-t-support-it.patch')
| -rw-r--r-- | meta-agl-profile-core/recipes-devtools/valgrind/valgrind/avoid-neon-for-targets-which-don-t-support-it.patch | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/meta-agl-profile-core/recipes-devtools/valgrind/valgrind/avoid-neon-for-targets-which-don-t-support-it.patch b/meta-agl-profile-core/recipes-devtools/valgrind/valgrind/avoid-neon-for-targets-which-don-t-support-it.patch new file mode 100644 index 000000000..5fcfec001 --- /dev/null +++ b/meta-agl-profile-core/recipes-devtools/valgrind/valgrind/avoid-neon-for-targets-which-don-t-support-it.patch @@ -0,0 +1,33 @@ +From 8facc29c3c56e6cf9cfef70986cf73876044a3fb Mon Sep 17 00:00:00 2001 +From: Andre McCurdy <armccurdy@gmail.com> +Date: Tue, 19 Jan 2016 16:42:36 -0800 +Subject: [PATCH] avoid neon for targets which don't support it + +The sh-mem-random.c test app tries to use neon loads and stores to +test 64-bit float copies when building for ARM. Allow it to do so if +possible, but fallback to C when building for ARM targets which don't +support neon. + +Upstream-Status: Pending + +Signed-off-by: Andre McCurdy <armccurdy@gmail.com> +--- + memcheck/tests/sh-mem-random.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/memcheck/tests/sh-mem-random.c b/memcheck/tests/sh-mem-random.c +index ae82248..816e139 100644 +--- a/memcheck/tests/sh-mem-random.c ++++ b/memcheck/tests/sh-mem-random.c +@@ -191,7 +191,7 @@ void do_test_at ( U1* arr ) + "emms" + : : "r"(arr+dst), "r"(arr+src) : "memory" + ); +-#elif defined(__linux__) && defined(__arm__) && !defined(__aarch64__) ++#elif defined(__linux__) && defined(__arm__) && defined(__ARM_NEON__) && !defined(__aarch64__) + /* On arm32, many compilers generate a 64-bit float move + using two 32 bit integer registers, which completely + defeats this test. Hence force a 64-bit NEON load and +-- +1.9.1 + |