Skip to contentSkip to conversation

Valgrind: update to 3.11.0

PATCH In review Alexander Kanavin 4 participants 8 messages Jan 8, 2016 – Jan 13, 2016

lore
Share & tools
lore
#0 lore raw

cover Valgrind: update to 3.11.0

This version of the patchset fixes the ppc32 build failures, and adds Andre McCurdy's fixes for arm.

The following changes since commit 0f3ad7c77aa0f8bb7641af1886e1420cdfa8419f:

scripts/yocto-layer: Avoids duplication of "meta-" prefix (2016-01-07 13:52:21 +0000)

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib akanavin/package-version-updates
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/package-version-updates

Alexander Kanavin (1):
valgrind: update to 3.11.0

Andre McCurdy (2):
valgrind: don't restrict to armv7a
valgrind: include aarch64 in COMPATIBLE_HOST

 ...s-that-fail-to-build-on-some-PPC32-config.patch |  51 +++++
 ...able-rt_sigpending-syscall-on-ppc64-linux.patch |  35 ---
 .../valgrind/valgrind/0002-remove-rpath.patch      |  35 +++
 .../valgrind/0004-Fix-out-of-tree-builds.patch     | 175 +++++++++++++++
 ...vg_test-wrapper-to-support-PTEST-formats.patch} |  87 ++++----
 .../valgrind/enable.building.on.4.x.kernel.patch   |  37 ----
 .../valgrind/valgrind/force-nostabs.patch          |  42 ----
 .../recipes-devtools/valgrind/valgrind/glibc.patch |  44 ----
 .../pass-maltivec-only-if-it-supported.patch       |  68 ------
 .../valgrind/remove-ppc-tests-failing-build.patch  |  75 -------
 .../valgrind/valgrind/sepbuildfix.patch            | 235 ---------------------
 .../{valgrind_3.10.1.bb => valgrind_3.11.0.bb}     |  41 ++--
 12 files changed, 329 insertions(+), 596 deletions(-)
 create mode 100644 meta/recipes-devtools/valgrind/valgrind/0001-Remove-tests-that-fail-to-build-on-some-PPC32-config.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/0001-valgrind-Enable-rt_sigpending-syscall-on-ppc64-linux.patch
 create mode 100644 meta/recipes-devtools/valgrind/valgrind/0002-remove-rpath.patch
 create mode 100644 meta/recipes-devtools/valgrind/valgrind/0004-Fix-out-of-tree-builds.patch
 rename meta/recipes-devtools/valgrind/valgrind/{add-ptest.patch => 0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch} (80%)
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/enable.building.on.4.x.kernel.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/force-nostabs.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/glibc.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/pass-maltivec-only-if-it-supported.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/remove-ppc-tests-failing-build.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/sepbuildfix.patch
 rename meta/recipes-devtools/valgrind/{valgrind_3.10.1.bb => valgrind_3.11.0.bb} (72%)
Signature · 1 line
2.6.4
#1 lore raw

PATCH 1/3 valgrind: update to 3.11.0

LICENSE checksums are changed due to a change in FSF address, or copyright years update.

Added patches:
0001-Remove-tests-that-fail-to-build-on-some-PPC32-config.patch replaces remove-ppc-tests-failing-build.patch and removes only those tests that are known to break the build on ppc32 configurations tested by poky autobuilders

Rebased patches:
sepbuildfix.patch rebased to 0004-Fix-out-of-tree-builds.patch add-ptest.patch rebased to 0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch

Removed patches:
force-nostabs.patch removed because it's patching lines that have been removed upstream remove-ppc-tests-failing-build.patch replaced with 0001-Remove-tests-that-fail-to-build-on-some-PPC32-config.patch enable.building.on.4.x.kernel.patch removed because the problem is fixed upstream
glibc.patch removed for the same reason

Removed backports:
pass-maltivec-only-if-it-supported.patch 0001-valgrind-Enable-rt_sigpending-syscall-on-ppc64-linux.patch

---
 ...s-that-fail-to-build-on-some-PPC32-config.patch |  51 +++++
 ...able-rt_sigpending-syscall-on-ppc64-linux.patch |  35 ---
 .../valgrind/valgrind/0002-remove-rpath.patch      |  35 +++
 .../valgrind/0004-Fix-out-of-tree-builds.patch     | 175 +++++++++++++++
 ...vg_test-wrapper-to-support-PTEST-formats.patch} |  87 ++++----
 .../valgrind/enable.building.on.4.x.kernel.patch   |  37 ----
 .../valgrind/valgrind/force-nostabs.patch          |  42 ----
 .../recipes-devtools/valgrind/valgrind/glibc.patch |  44 ----
 .../pass-maltivec-only-if-it-supported.patch       |  68 ------
 .../valgrind/remove-ppc-tests-failing-build.patch  |  75 -------
 .../valgrind/valgrind/sepbuildfix.patch            | 235 ---------------------
 .../{valgrind_3.10.1.bb => valgrind_3.11.0.bb}     |  33 ++-
 12 files changed, 324 insertions(+), 593 deletions(-)
 create mode 100644 meta/recipes-devtools/valgrind/valgrind/0001-Remove-tests-that-fail-to-build-on-some-PPC32-config.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/0001-valgrind-Enable-rt_sigpending-syscall-on-ppc64-linux.patch
 create mode 100644 meta/recipes-devtools/valgrind/valgrind/0002-remove-rpath.patch
 create mode 100644 meta/recipes-devtools/valgrind/valgrind/0004-Fix-out-of-tree-builds.patch
 rename meta/recipes-devtools/valgrind/valgrind/{add-ptest.patch => 0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch} (80%)
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/enable.building.on.4.x.kernel.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/force-nostabs.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/glibc.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/pass-maltivec-only-if-it-supported.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/remove-ppc-tests-failing-build.patch
 delete mode 100644 meta/recipes-devtools/valgrind/valgrind/sepbuildfix.patch
 rename meta/recipes-devtools/valgrind/{valgrind_3.10.1.bb => valgrind_3.11.0.bb} (77%)
meta/recipes-devtools/valgrind/valgrind/0001-Remove-tests-that-fail-to-build-on-some-PPC32-config.patch new file +51 -0
new file mode 100644
index 0000000..a78e195
@@ -0,0 +1,51 @@
+From 9762fd23e1f1db66d4b977c694a17d3bca3fe99a Mon Sep 17 00:00:00 2001
+From: Alexander Kanavin <[email protected]>
+Date: Fri, 8 Jan 2016 16:36:29 +0200
+Subject: [PATCH] Remove tests that fail to build on some PPC32 configurations
+
+Failures are documented here:
+http://errors.yoctoproject.org/Errors/Search/?items=10&query=862d702fbb99e484631315aa44b9e46f8fc567da&filter=valgrind&type=recipe
+
+Signed-off-by: Alexander Kanavin <[email protected]>
+Upstream-Status: Pending
+---
+ memcheck/tests/ppc32/Makefile.am | 2 +-
+ none/tests/ppc32/Makefile.am     | 4 ++--
+ 2 files changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/memcheck/tests/ppc32/Makefile.am b/memcheck/tests/ppc32/Makefile.am
+index 26b95a2..8f05743 100644
+--- a/memcheck/tests/ppc32/Makefile.am
++++ b/memcheck/tests/ppc32/Makefile.am
+@@ -10,7 +10,7 @@ EXTRA_DIST = $(noinst_SCRIPTS) \
+ 	power_ISA2_07.stderr.exp power_ISA2_07.vgtest
+ 
+ check_PROGRAMS = \
+-	power_ISA2_05 power_ISA2_07
++	power_ISA2_07
+ 
+ power_ISA2_05_CFLAGS = $(AM_CFLAGS) $(WERROR) -Winline -Wall -Wshadow -g \
+ 		-I$(top_srcdir)/include @FLAG_M32@
+diff --git a/none/tests/ppc32/Makefile.am b/none/tests/ppc32/Makefile.am
+index 196239e..0fe3425 100644
+--- a/none/tests/ppc32/Makefile.am
++++ b/none/tests/ppc32/Makefile.am
+@@ -50,13 +50,13 @@ EXTRA_DIST = \
+ 
+ check_PROGRAMS = \
+ 	allexec \
+-	lsw jm-insns round \
++	lsw \
+ 	test_isa_2_06_part1 test_isa_2_06_part2 test_isa_2_06_part3 \
+ 	test_dfp1 test_dfp2 test_dfp3 test_dfp4 test_dfp5 \
+ 	test_isa_2_07_part1 test_isa_2_07_part2 \
+ 	test_tm test_touch_tm ldst_multiple data-cache-instructions \
+ 	test_fx test_gx \
+-	testVMX twi tw xlc_dbl_u32 power5+_round power6_bcmp \
++	twi tw xlc_dbl_u32 power6_bcmp \
+ 	bug129390-ppc32 bug139050-ppc32 \
+ 	ldstrev mftocrf mcrfs
+ 
+-- 
+2.6.4
+
meta/recipes-devtools/valgrind/valgrind/0001-valgrind-Enable-rt_sigpending-syscall-on-ppc64-linux.patch deleted +0 -35
deleted file mode 100644
index 56bb5f5..0000000
@@ -1,35 +0,0 @@
-From 1a8006f56342dae9f7100a3c33d80873676e0404 Mon Sep 17 00:00:00 2001
-From: Li Zhou <[email protected]>
-Date: Mon, 24 Aug 2015 03:55:18 -0400
-Subject: [PATCH] valgrind: Enable rt_sigpending syscall on ppc64 linux
-
-New Revision: 15133
-Enable rt_sigpending syscall on ppc64 linux.
-Patch from Thomas Huth <[email protected]>
-
-Get the patch from valgrind upstream:
-http://valgrind.10908.n7.nabble.com/Valgrind-r15133-in-trunk-NEWS-coregrind-m-syswrap-syswrap-ppc64-linux-c-td54589.html
-
-Upstream-Status: backport
-
-Signed-off-by: Li Zhou <[email protected]>
----
- coregrind/m_syswrap/syswrap-ppc64-linux.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/coregrind/m_syswrap/syswrap-ppc64-linux.c b/coregrind/m_syswrap/syswrap-ppc64-linux.c
-index 5946ee1..8aaa1d7 100644
---- a/coregrind/m_syswrap/syswrap-ppc64-linux.c
-+++ b/coregrind/m_syswrap/syswrap-ppc64-linux.c
-@@ -887,7 +887,7 @@ static SyscallTableEntry syscall_table[] = {
-    LINXY(__NR_rt_sigaction,      sys_rt_sigaction),       // 173
-    LINXY(__NR_rt_sigprocmask,    sys_rt_sigprocmask),     // 174
- 
--// _____(__NR_rt_sigpending,     sys_rt_sigpending),      // 175
-+   LINXY(__NR_rt_sigpending,     sys_rt_sigpending),      // 175
-    LINXY(__NR_rt_sigtimedwait,   sys_rt_sigtimedwait),    // 176
-    LINXY(__NR_rt_sigqueueinfo,   sys_rt_sigqueueinfo),    // 177
-    LINX_(__NR_rt_sigsuspend,     sys_rt_sigsuspend),      // 178
--- 
-1.9.1
-
meta/recipes-devtools/valgrind/valgrind/0002-remove-rpath.patch new file +35 -0
new file mode 100644
index 0000000..e9112da
@@ -0,0 +1,35 @@
+From f96cf1f4eaa72860ab8b5e18ad10fdc704d78c5f Mon Sep 17 00:00:00 2001
+From: Alexander Kanavin <[email protected]>
+Date: Tue, 15 Dec 2015 15:01:34 +0200
+Subject: [PATCH 2/5] remove rpath
+
+Upstream-Status: Inappropriate [embedded config]
+Signed-off-by: Saul Wold <[email protected]>
+---
+ none/tests/Makefile.am | 3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/none/tests/Makefile.am b/none/tests/Makefile.am
+index 54f2a7e..25b0f49 100644
+--- a/none/tests/Makefile.am
++++ b/none/tests/Makefile.am
+@@ -326,7 +326,6 @@ threadederrno_CFLAGS	+= --std=c99
+ endif
+ tls_SOURCES		= tls.c tls2.c
+ tls_DEPENDENCIES	= tls.so tls2.so
+-tls_LDFLAGS		= -Wl,-rpath,$(abs_top_builddir)/none/tests
+ tls_LDADD		= tls.so tls2.so -lpthread
+ tls_so_SOURCES		= tls_so.c
+ tls_so_DEPENDENCIES	= tls2.so
+@@ -334,7 +333,7 @@ if VGCONF_OS_IS_DARWIN
+  tls_so_LDFLAGS		= -dynamic -dynamiclib -all_load -fpic
+  tls_so_LDADD		= `pwd`/tls2.so
+ else
+- tls_so_LDFLAGS		= -Wl,-rpath,$(abs_top_builddir)/none/tests -shared -fPIC
++ tls_so_LDFLAGS		= -shared -fPIC
+  tls_so_LDADD		= tls2.so
+ endif
+ tls_so_CFLAGS		= $(AM_CFLAGS) -fPIC
+-- 
+2.6.2
+
meta/recipes-devtools/valgrind/valgrind/0004-Fix-out-of-tree-builds.patch new file +175 -0

175 lines not on this page · raw message

meta/recipes-devtools/valgrind/valgrind/0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch renamed from meta/recipes-devtools/valgrind/valgrind/add-ptest.patch +48 -39

212 lines not on this page · raw message

meta/recipes-devtools/valgrind/valgrind/enable.building.on.4.x.kernel.patch deleted +0 -37
deleted file mode 100644
index 300f2f1..0000000
@@ -1,37 +0,0 @@
-Enable building valgrind on host with 4.x kernel.
-
-For OpenEmbedded builds we should be checking something like
-OLDEST_KERNEL instead of `uname -r`, but this is good enough for now.
-
-Building on 4.x* currently fails with:
-  configure:5556: checking for the kernel version
-  configure:5579: result: unsupported (4.0.0-rc3-00111-gaffb817)
-  configure:5581: error: Valgrind works on kernels 2.4, 2.6
-
-Upstream-Status: Pending
-Signed-off-by: Martin Jansa <[email protected]>
-
---- valgrind-3.9.0/configure.ac.orig	2015-03-13 19:17:01.247310868 +0100
-+++ valgrind-3.9.0/configure.ac	2015-03-13 19:19:27.388316108 +0100
-@@ -276,9 +276,9 @@
-         kernel=`uname -r`
- 
-         case "${kernel}" in
--             2.6.*|3.*) 
--        	    AC_MSG_RESULT([2.6.x/3.x family (${kernel})])
--        	    AC_DEFINE([KERNEL_2_6], 1, [Define to 1 if you're using Linux 2.6.x or Linux 3.x])
-+             2.6.*|3.*|4.*) 
-+        	    AC_MSG_RESULT([2.6.x/3.x/4.x family (${kernel})])
-+        	    AC_DEFINE([KERNEL_2_6], 1, [Define to 1 if you're using Linux 2.6.x or Linux 3.x or Linux 4.x])
-         	    ;;
- 
-              2.4.*) 
-@@ -288,7 +288,7 @@
- 
-              *) 
-         	    AC_MSG_RESULT([unsupported (${kernel})])
--        	    AC_MSG_ERROR([Valgrind works on kernels 2.4, 2.6])
-+        	    AC_MSG_ERROR([Valgrind works on kernels 2.4, 2.6, 3.x, 4.x])
-         	    ;;
-         esac
- 
meta/recipes-devtools/valgrind/valgrind/force-nostabs.patch deleted +0 -42

42 lines not on this page · raw message

meta/recipes-devtools/valgrind/valgrind/glibc.patch deleted +0 -44

44 lines not on this page · raw message

meta/recipes-devtools/valgrind/valgrind/pass-maltivec-only-if-it-supported.patch deleted +0 -68

68 lines not on this page · raw message

meta/recipes-devtools/valgrind/valgrind/remove-ppc-tests-failing-build.patch deleted +0 -75

75 lines not on this page · raw message

meta/recipes-devtools/valgrind/valgrind/sepbuildfix.patch deleted +0 -235

235 lines not on this page · raw message

meta/recipes-devtools/valgrind/valgrind_3.11.0.bb renamed from meta/recipes-devtools/valgrind/valgrind_3.10.1.bb +15 -18
similarity index 77%
rename from meta/recipes-devtools/valgrind/valgrind_3.10.1.bb
rename to meta/recipes-devtools/valgrind/valgrind_3.11.0.bb
index c1c11d4..0823144 100644
@@ -2,10 +2,10 @@ SUMMARY = "Valgrind memory debugger and instrumentation framework"
 HOMEPAGE = "http://valgrind.org/"
 BUGTRACKER = "http://valgrind.org/support/bug_reports.html"
 LICENSE = "GPLv2 & GPLv2+ & BSD"
-LIC_FILES_CHKSUM = "file://COPYING;md5=c46082167a314d785d012a244748d803 \
-                    file://include/pub_tool_basics.h;beginline=1;endline=29;md5=e7071929a50d4b0fc27a3014b315b0f7 \
-                    file://include/valgrind.h;beginline=1;endline=56;md5=92df8a1bde56fe2af70931ff55f6622f \
-                    file://COPYING.DOCS;md5=8fdeb5abdb235a08e76835f8f3260215"
+LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
+                    file://include/pub_tool_basics.h;beginline=1;endline=29;md5=ebb8e640ef633f940c425686c873f9fa \
+                    file://include/valgrind.h;beginline=1;endline=56;md5=4b5e24908e53016ea561c45f4234a327 \
+                    file://COPYING.DOCS;md5=24ea4c7092233849b4394699333b5c56"
 
 X11DEPENDS = "virtual/libx11"
 DEPENDS = "${@bb.utils.contains('DISTRO_FEATURES', 'x11', '${X11DEPENDS}', '', d)} \
@@ -15,28 +15,21 @@ DEPENDS = "${@bb.utils.contains('DISTRO_FEATURES', 'x11', '${X11DEPENDS}', '', d
 SRC_URI = "http://www.valgrind.org/downloads/valgrind-${PV}.tar.bz2 \
            file://fixed-perl-path.patch \
            file://Added-support-for-PPC-instructions-mfatbu-mfatbl.patch \
-           file://sepbuildfix.patch \
-           file://glibc.patch \
-           file://force-nostabs.patch \
            file://remove-arm-variant-specific.patch \
-           file://remove-ppc-tests-failing-build.patch \
-           file://valgrind-remove-rpath.patch \
-           file://enable.building.on.4.x.kernel.patch \
-           file://add-ptest.patch \
-           file://pass-maltivec-only-if-it-supported.patch \
            file://run-ptest \
-           file://0001-valgrind-Enable-rt_sigpending-syscall-on-ppc64-linux.patch \
            file://11_mips-link-tool.patch \
-          "
+           file://0002-remove-rpath.patch \
+           file://0004-Fix-out-of-tree-builds.patch \
+           file://0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch \
+           file://0001-Remove-tests-that-fail-to-build-on-some-PPC32-config.patch \
+           "
 
-SRC_URI[md5sum] = "60ddae962bc79e7c95cfc4667245707f"
-SRC_URI[sha256sum] = "fa253dc26ddb661b6269df58144eff607ea3f76a9bcfe574b0c7726e1dfcb997"
+SRC_URI[md5sum] = "4ea62074da73ae82e0162d6550d3f129"
+SRC_URI[sha256sum] = "6c396271a8c1ddd5a6fb9abe714ea1e8a86fce85b30ab26b4266aeb4c2413b42"
 
 COMPATIBLE_HOST = '(i.86|x86_64|mips|powerpc|powerpc64).*-linux'
 COMPATIBLE_HOST_armv7a = 'arm.*-linux'
 
-PR = "r1"
-
 inherit autotools ptest
 
 EXTRA_OECONF = "--enable-tls --without-mpicc"
@@ -58,6 +51,10 @@ RRECOMMENDS_${PN} += "${TCLIBC}-dbg"
 
 RDEPENDS_${PN}-ptest += " sed perl glibc-utils perl-module-file-glob"
 
+# One of the tests contains a bogus interpreter path on purpose, and QA
+# check complains about it
+INSANE_SKIP_${PN}-ptest += "file-rdeps"
+
 do_compile_ptest() {
     oe_runmake check CFLAGS="${CFLAGS} -O0" CXXFLAGS="${CXXFLAGS} -O0"
 }
Signature · 1 line
2.6.4
#2 lore raw

PATCH 2/3 valgrind: don't restrict to armv7a

In reply to Alexander Kanavin

From: Andre McCurdy <[email protected]>

Valgrind has been tested on armv5te/qemuarm, so it seems that valgrind's configure check for armv7 is over cautious.

---
 meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +5 -3
index 0823144..575db35 100644
@@ -27,14 +27,16 @@ SRC_URI = "http://www.valgrind.org/downloads/valgrind-${PV}.tar.bz2 \
 SRC_URI[md5sum] = "4ea62074da73ae82e0162d6550d3f129"
 SRC_URI[sha256sum] = "6c396271a8c1ddd5a6fb9abe714ea1e8a86fce85b30ab26b4266aeb4c2413b42"
 
-COMPATIBLE_HOST = '(i.86|x86_64|mips|powerpc|powerpc64).*-linux'
-COMPATIBLE_HOST_armv7a = 'arm.*-linux'
+COMPATIBLE_HOST = '(i.86|x86_64|arm|mips|powerpc|powerpc64).*-linux'
 
 inherit autotools ptest
 
 EXTRA_OECONF = "--enable-tls --without-mpicc"
-EXTRA_OECONF_armv7a = "--enable-tls -host=armv7-none-linux-gnueabi --without-mpicc"
 EXTRA_OECONF += "${@['--enable-only32bit','--enable-only64bit'][d.getVar('SITEINFO_BITS', True) != '32']}"
+
+# valgrind checks host_cpu "armv7*)", so we need to over-ride the autotools.bbclass default --host option
+EXTRA_OECONF_append_arm = " --host=armv7${HOST_VENDOR}-${HOST_OS}"
+
 EXTRA_OEMAKE = "-w"
 
 CFLAGS_append_libc-uclibc = " -D__UCLIBC__ "
Signature · 1 line
2.6.4
#3 lore raw

Re: [PATCH 2/3] valgrind: don't restrict to armv7a

Hi Alexander

I got valgrind do_compile error:

MACHINE = "qemuarm"

$ bitbake valgrind

warning: switch -mcpu=cortex-a8 conflicts with -march=armv5e switch

| {standard input}:25: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:28: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:30: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:31: Error: selected processor does not support ARM mode `movw r3,#0xAAAA'
| {standard input}:40: Error: selected processor does not support ARM mode `movw r3,#0x5555'
| {standard input}:61: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:64: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:66: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:94: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:95: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:96: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:135: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:136: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:137: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'

Thanks!

//dengke

Quoted 35 lines · Alexander Kanavin

From: Andre McCurdy <[email protected]>

Valgrind has been tested on armv5te/qemuarm, so it seems that valgrind's configure check for armv7 is over cautious.

---
  meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++---
  1 file changed, 5 insertions(+), 3 deletions(-)
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +5 -3
index 0823144..575db35 100644
@@ -27,14 +27,16 @@ SRC_URI = "http://www.valgrind.org/downloads/valgrind-${PV}.tar.bz2 \
  SRC_URI[md5sum] = "4ea62074da73ae82e0162d6550d3f129"
  SRC_URI[sha256sum] = "6c396271a8c1ddd5a6fb9abe714ea1e8a86fce85b30ab26b4266aeb4c2413b42"
 
-COMPATIBLE_HOST = '(i.86|x86_64|mips|powerpc|powerpc64).*-linux'
-COMPATIBLE_HOST_armv7a = 'arm.*-linux'
+COMPATIBLE_HOST = '(i.86|x86_64|arm|mips|powerpc|powerpc64).*-linux'
 
  inherit autotools ptest
 
  EXTRA_OECONF = "--enable-tls --without-mpicc"
-EXTRA_OECONF_armv7a = "--enable-tls -host=armv7-none-linux-gnueabi --without-mpicc"
  EXTRA_OECONF += "${@['--enable-only32bit','--enable-only64bit'][d.getVar('SITEINFO_BITS', True) != '32']}"
+
+# valgrind checks host_cpu "armv7*)", so we need to over-ride the autotools.bbclass default --host option
+EXTRA_OECONF_append_arm = " --host=armv7${HOST_VENDOR}-${HOST_OS}"
+
  EXTRA_OEMAKE = "-w"
 
  CFLAGS_append_libc-uclibc = " -D__UCLIBC__ "
#4 lore raw

Re: [PATCH 2/3] valgrind: don't restrict to armv7a

In reply to Alexander Kanavin

Hi Alexander

I got valgrind do_compile error:

MACHINE = "qemuarm"

$ bitbake valgrind

warning: switch -mcpu=cortex-a8 conflicts with -march=armv5e switch

| {standard input}:25: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:28: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:30: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:31: Error: selected processor does not support ARM mode `movw r3,#0xAAAA'
| {standard input}:40: Error: selected processor does not support ARM mode `movw r3,#0x5555'
| {standard input}:61: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:64: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:66: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:94: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:95: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:96: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:135: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:136: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:137: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'

Thanks!

//dengke

Quoted 35 lines · Alexander Kanavin

From: Andre McCurdy <[email protected]>

Valgrind has been tested on armv5te/qemuarm, so it seems that valgrind's configure check for armv7 is over cautious.

---
  meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++---
  1 file changed, 5 insertions(+), 3 deletions(-)
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +5 -3
index 0823144..575db35 100644
@@ -27,14 +27,16 @@ SRC_URI = "http://www.valgrind.org/downloads/valgrind-${PV}.tar.bz2 \
  SRC_URI[md5sum] = "4ea62074da73ae82e0162d6550d3f129"
  SRC_URI[sha256sum] = "6c396271a8c1ddd5a6fb9abe714ea1e8a86fce85b30ab26b4266aeb4c2413b42"
 
-COMPATIBLE_HOST = '(i.86|x86_64|mips|powerpc|powerpc64).*-linux'
-COMPATIBLE_HOST_armv7a = 'arm.*-linux'
+COMPATIBLE_HOST = '(i.86|x86_64|arm|mips|powerpc|powerpc64).*-linux'
 
  inherit autotools ptest
 
  EXTRA_OECONF = "--enable-tls --without-mpicc"
-EXTRA_OECONF_armv7a = "--enable-tls -host=armv7-none-linux-gnueabi --without-mpicc"
  EXTRA_OECONF += "${@['--enable-only32bit','--enable-only64bit'][d.getVar('SITEINFO_BITS', True) != '32']}"
+
+# valgrind checks host_cpu "armv7*)", so we need to over-ride the autotools.bbclass default --host option
+EXTRA_OECONF_append_arm = " --host=armv7${HOST_VENDOR}-${HOST_OS}"
+
  EXTRA_OEMAKE = "-w"
 
  CFLAGS_append_libc-uclibc = " -D__UCLIBC__ "
#5 lore raw

Re: [PATCH 2/3] valgrind: don't restrict to armv7a

Quoted 28 lines · On Tue, Jan 12, 2016 at 6:18 PM, [email protected]…

Hi Alexander

I got valgrind do_compile error:

MACHINE = "qemuarm"

$ bitbake valgrind

warning: switch -mcpu=cortex-a8 conflicts with -march=armv5e switch | {standard input}:25: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:28: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:30: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:31: Error: selected processor does not support ARM mode `movw r3,#0xAAAA'
| {standard input}:40: Error: selected processor does not support ARM mode `movw r3,#0x5555'
| {standard input}:61: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:64: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:66: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:94: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:95: Error: selected processor does not support ARM mode `uxth r1,r0'

Quoted 8 lines

| {standard input}:96: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:135: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:136: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:137: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'

Apparently Khem had this working prior to the update to valgrind v3.11

http://lists.openembedded.org/pipermail/openembedded-core/2015-December/114340.html

Looking at the code I don't see any easy way to build for armv5 though. Maybe it's hackable, but the result probably wouldn't be suitable for oe-core.

Probably the best solution is to restore the blacklisting of armv6 and below. I'll send a patch.

Quoted 57 lines

Thanks!

//dengke

On 2016年01月08日 22:57, Alexander Kanavin wrote:

From: Andre McCurdy <[email protected]>

Valgrind has been tested on armv5te/qemuarm, so it seems that valgrind's configure check for armv7 is over cautious.

---
 meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +0 -0
index 0823144..575db35 100644
@@ -27,14 +27,16 @@ SRC_URI =
 "http://www.valgrind.org/downloads/valgrind-${PV}.tar.bz2 \
 SRC_URI[md5sum] = "4ea62074da73ae82e0162d6550d3f129"
 SRC_URI[sha256sum] =

"6c396271a8c1ddd5a6fb9abe714ea1e8a86fce85b30ab26b4266aeb4c2413b42"

meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +1 -4
-COMPATIBLE_HOST = '(i.86|x86_64|mips|powerpc|powerpc64).*-linux'
-COMPATIBLE_HOST_armv7a = 'arm.*-linux'
+COMPATIBLE_HOST = '(i.86|x86_64|arm|mips|powerpc|powerpc64).*-linux'
 
 inherit autotools ptest
 
 EXTRA_OECONF = "--enable-tls --without-mpicc"
-EXTRA_OECONF_armv7a = "--enable-tls -host=armv7-none-linux-gnueabi
--without-mpicc"
 EXTRA_OECONF +=

"${@['--enable-only32bit','--enable-only64bit'][d.getVar('SITEINFO_BITS', True) != '32']}"

meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +2 -0
+
+# valgrind checks host_cpu "armv7*)", so we need to over-ride the

autotools.bbclass default --host option

meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +2 -1
+EXTRA_OECONF_append_arm = " --host=armv7${HOST_VENDOR}-${HOST_OS}"
+
 EXTRA_OEMAKE = "-w"
 
 CFLAGS_append_libc-uclibc = " -D__UCLIBC__ "
 
 
 
--

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#6 lore raw

Re: [PATCH 2/3] valgrind: don't restrict to armv7a

Quoted 10 lines · Andre McCurdy
Quoted 8 lines · On Tue, Jan 12, 2016 at 6:18 PM, [email protected]…

Hi Alexander

I got valgrind do_compile error:

MACHINE = "qemuarm"

$ bitbake valgrind

warning: switch -mcpu=cortex-a8 conflicts with -march=armv5e switch

-mcpu=cortex-a8 used for armv5 may not be right but patches from

https://bugs.kde.org/show_bug.cgi?id=248998

are helpful.

Quoted 102 lines
Quoted 20 lines

| {standard input}:25: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:28: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:30: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:31: Error: selected processor does not support ARM mode `movw r3,#0xAAAA'
| {standard input}:40: Error: selected processor does not support ARM mode `movw r3,#0x5555'
| {standard input}:61: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:64: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:66: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:94: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:95: Error: selected processor does not support ARM mode `uxth r1,r0'

Quoted 8 lines

| {standard input}:96: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'
| {standard input}:135: Error: selected processor does not support ARM mode `movw r3,#:lower16:primary_map'
| {standard input}:136: Error: selected processor does not support ARM mode `uxth r1,r0'
| {standard input}:137: Error: selected processor does not support ARM mode `movt r3,#:upper16:primary_map'

Apparently Khem had this working prior to the update to valgrind v3.11

http://lists.openembedded.org/pipermail/openembedded-core/2015-December/114340.html

Looking at the code I don't see any easy way to build for armv5 though. Maybe it's hackable, but the result probably wouldn't be suitable for oe-core.

Probably the best solution is to restore the blacklisting of armv6 and below. I'll send a patch.

Quoted 52 lines

Thanks!

//dengke

On 2016年01月08日 22:57, Alexander Kanavin wrote:

From: Andre McCurdy <[email protected]>

Valgrind has been tested on armv5te/qemuarm, so it seems that valgrind's configure check for armv7 is over cautious.

---
 meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +0 -0
index 0823144..575db35 100644
@@ -27,14 +27,16 @@ SRC_URI =
 "http://www.valgrind.org/downloads/valgrind-${PV}.tar.bz2 \
 SRC_URI[md5sum] = "4ea62074da73ae82e0162d6550d3f129"
 SRC_URI[sha256sum] =

"6c396271a8c1ddd5a6fb9abe714ea1e8a86fce85b30ab26b4266aeb4c2413b42"

meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +1 -4
-COMPATIBLE_HOST = '(i.86|x86_64|mips|powerpc|powerpc64).*-linux'
-COMPATIBLE_HOST_armv7a = 'arm.*-linux'
+COMPATIBLE_HOST = '(i.86|x86_64|arm|mips|powerpc|powerpc64).*-linux'
 
 inherit autotools ptest
 
 EXTRA_OECONF = "--enable-tls --without-mpicc"
-EXTRA_OECONF_armv7a = "--enable-tls -host=armv7-none-linux-gnueabi
--without-mpicc"
 EXTRA_OECONF +=

"${@['--enable-only32bit','--enable-only64bit'][d.getVar('SITEINFO_BITS', True) != '32']}"

meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +2 -0
+
+# valgrind checks host_cpu "armv7*)", so we need to over-ride the

autotools.bbclass default --host option

meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +2 -1
+EXTRA_OECONF_append_arm = " --host=armv7${HOST_VENDOR}-${HOST_OS}"
+
 EXTRA_OEMAKE = "-w"
 
 CFLAGS_append_libc-uclibc = " -D__UCLIBC__ "
 
 
 
--
Quoted 5 lines

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#7 lore raw

PATCH 3/3 valgrind: include aarch64 in COMPATIBLE_HOST

In reply to Alexander Kanavin

From: Andre McCurdy <[email protected]>

Valgrind has supported aarch64 since v3.10.0.

---
 meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +1 -1
index 575db35..00217fa 100644
@@ -27,7 +27,7 @@ SRC_URI = "http://www.valgrind.org/downloads/valgrind-${PV}.tar.bz2 \
 SRC_URI[md5sum] = "4ea62074da73ae82e0162d6550d3f129"
 SRC_URI[sha256sum] = "6c396271a8c1ddd5a6fb9abe714ea1e8a86fce85b30ab26b4266aeb4c2413b42"
 
-COMPATIBLE_HOST = '(i.86|x86_64|arm|mips|powerpc|powerpc64).*-linux'
+COMPATIBLE_HOST = '(i.86|x86_64|arm|aarch64|mips|powerpc|powerpc64).*-linux'
 
 inherit autotools ptest
 
Signature · 1 line
2.6.4