* [PATCH 0/3] valgrind fixes
@ 2015-12-22 23:57 Andre McCurdy
2015-12-22 23:57 ` [PATCH 1/3] security_flags.inc: disable -fstack-protector-XXX for valgrind Andre McCurdy
` (2 more replies)
0 siblings, 3 replies; 12+ messages in thread
From: Andre McCurdy @ 2015-12-22 23:57 UTC (permalink / raw)
To: openembedded-core
Andre McCurdy (3):
security_flags.inc: disable -fstack-protector-XXX for valgrind
valgrind: don't restrict to armv7a
valgrind: include aarch64 in COMPATIBLE_HOST
meta/conf/distro/include/security_flags.inc | 2 +-
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++---
2 files changed, 6 insertions(+), 4 deletions(-)
--
1.9.1
^ permalink raw reply [flat|nested] 12+ messages in thread* [PATCH 1/3] security_flags.inc: disable -fstack-protector-XXX for valgrind 2015-12-22 23:57 [PATCH 0/3] valgrind fixes Andre McCurdy @ 2015-12-22 23:57 ` Andre McCurdy 2015-12-22 23:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Andre McCurdy 2015-12-22 23:58 ` [PATCH 3/3] valgrind: include aarch64 in COMPATIBLE_HOST Andre McCurdy 2 siblings, 0 replies; 12+ messages in thread From: Andre McCurdy @ 2015-12-22 23:57 UTC (permalink / raw) To: openembedded-core Valgrind (v3.11.0) expects to build with stack protection disabled and includes -fno-stack-protector in its default CFLAGS. However, the CFLAGS provided by OE are included on the compiler command line after the defaults so any -fstack-protector-all / -fstack-protector-strong option provided by security_flags.inc will cause problems. | .../build-bcm97425vms/tmp/work/mips32el-rdk-linux/valgrind/3.11.0-r0/valgrind-3.11.0/coregrind/m_mallocfree.c:892: undefined reference to `__stack_chk_guard' | .../build-bcm97425vms/tmp/work/mips32el-rdk-linux/valgrind/3.11.0-r0/valgrind-3.11.0/coregrind/m_mallocfree.c:947: undefined reference to `__stack_chk_fail' Signed-off-by: Andre McCurdy <armccurdy@gmail.com> --- meta/conf/distro/include/security_flags.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/conf/distro/include/security_flags.inc b/meta/conf/distro/include/security_flags.inc index 14ac0bf..1795750 100644 --- a/meta/conf/distro/include/security_flags.inc +++ b/meta/conf/distro/include/security_flags.inc @@ -84,7 +84,7 @@ SECURITY_CFLAGS_pn-python-numpy = "${SECURITY_NO_PIE_CFLAGS}" SECURITY_CFLAGS_pn-python3 = "${SECURITY_NO_PIE_CFLAGS}" SECURITY_CFLAGS_pn-tcl = "${SECURITY_NO_PIE_CFLAGS}" SECURITY_CFLAGS_pn-tiff = "${SECURITY_NO_PIE_CFLAGS}" -SECURITY_CFLAGS_pn-valgrind = "${SECURITY_NO_PIE_CFLAGS}" +SECURITY_CFLAGS_pn-valgrind = "" SECURITY_CFLAGS_pn-zlib = "${SECURITY_NO_PIE_CFLAGS}" # These 2 have text relco errors with the pie options enabled -- 1.9.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH 2/3] valgrind: don't restrict to armv7a 2015-12-22 23:57 [PATCH 0/3] valgrind fixes Andre McCurdy 2015-12-22 23:57 ` [PATCH 1/3] security_flags.inc: disable -fstack-protector-XXX for valgrind Andre McCurdy @ 2015-12-22 23:57 ` Andre McCurdy 2016-01-07 21:03 ` Andre McCurdy 2015-12-22 23:58 ` [PATCH 3/3] valgrind: include aarch64 in COMPATIBLE_HOST Andre McCurdy 2 siblings, 1 reply; 12+ messages in thread From: Andre McCurdy @ 2015-12-22 23:57 UTC (permalink / raw) To: openembedded-core Valgrind has been tested on armv5te/qemuarm, so it seems that valgrind's configure check for armv7 is over cautious. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> --- meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb index 3dc3cc1..bb3f6e1 100644 --- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb @@ -26,14 +26,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" do_install_append () { -- 1.9.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: [PATCH 2/3] valgrind: don't restrict to armv7a 2015-12-22 23:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Andre McCurdy @ 2016-01-07 21:03 ` Andre McCurdy 2016-01-07 21:39 ` Burton, Ross 0 siblings, 1 reply; 12+ messages in thread From: Andre McCurdy @ 2016-01-07 21:03 UTC (permalink / raw) To: OE Core mailing list On Tue, Dec 22, 2015 at 3:57 PM, Andre McCurdy <armccurdy@gmail.com> wrote: > Valgrind has been tested on armv5te/qemuarm, so it seems > that valgrind's configure check for armv7 is over cautious. Ping. This is more urgent now that arch-armv7ve.inc has been merged to oe-core master. > Signed-off-by: Andre McCurdy <armccurdy@gmail.com> > --- > meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > index 3dc3cc1..bb3f6e1 100644 > --- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > +++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > @@ -26,14 +26,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" > > do_install_append () { > -- > 1.9.1 > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 2/3] valgrind: don't restrict to armv7a 2016-01-07 21:03 ` Andre McCurdy @ 2016-01-07 21:39 ` Burton, Ross 2016-01-08 12:43 ` Alexander Kanavin 0 siblings, 1 reply; 12+ messages in thread From: Burton, Ross @ 2016-01-07 21:39 UTC (permalink / raw) To: Andre McCurdy; +Cc: OE Core mailing list [-- Attachment #1: Type: text/plain, Size: 295 bytes --] On 7 January 2016 at 21:03, Andre McCurdy <armccurdy@gmail.com> wrote: > Ping. This is more urgent now that arch-armv7ve.inc has been merged to > oe-core master. > Sadly 3.11 totally breaks on PPC, so that's blocking. Maybe rebase the patch to master before the 3.11 upgrade? Ross [-- Attachment #2: Type: text/html, Size: 687 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 2/3] valgrind: don't restrict to armv7a 2016-01-07 21:39 ` Burton, Ross @ 2016-01-08 12:43 ` Alexander Kanavin 0 siblings, 0 replies; 12+ messages in thread From: Alexander Kanavin @ 2016-01-08 12:43 UTC (permalink / raw) To: openembedded-core On 01/07/2016 11:39 PM, Burton, Ross wrote: > > On 7 January 2016 at 21:03, Andre McCurdy <armccurdy@gmail.com > <mailto:armccurdy@gmail.com>> wrote: > > Ping. This is more urgent now that arch-armv7ve.inc has been merged to > oe-core master. > > > Sadly 3.11 totally breaks on PPC, so that's blocking. Maybe rebase the > patch to master before the 3.11 upgrade? I'll fix the PPC breakage and resend (with Andre's fix commits if they aren't yet in master against old version by then). Alex ^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH 3/3] valgrind: include aarch64 in COMPATIBLE_HOST 2015-12-22 23:57 [PATCH 0/3] valgrind fixes Andre McCurdy 2015-12-22 23:57 ` [PATCH 1/3] security_flags.inc: disable -fstack-protector-XXX for valgrind Andre McCurdy 2015-12-22 23:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Andre McCurdy @ 2015-12-22 23:58 ` Andre McCurdy 2 siblings, 0 replies; 12+ messages in thread From: Andre McCurdy @ 2015-12-22 23:58 UTC (permalink / raw) To: openembedded-core Valgrind has supported aarch64 since v3.10.0. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> --- meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb index bb3f6e1..293dd2b 100644 --- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb @@ -26,7 +26,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 -- 1.9.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH 0/3] Valgrind: update to 3.11.0
@ 2016-01-08 14:57 Alexander Kanavin
2016-01-08 14:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Alexander Kanavin
0 siblings, 1 reply; 12+ messages in thread
From: Alexander Kanavin @ 2016-01-08 14:57 UTC (permalink / raw)
To: openembedded-core
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%)
--
2.6.4
^ permalink raw reply [flat|nested] 12+ messages in thread* [PATCH 2/3] valgrind: don't restrict to armv7a 2016-01-08 14:57 [PATCH 0/3] Valgrind: update to 3.11.0 Alexander Kanavin @ 2016-01-08 14:57 ` Alexander Kanavin 2016-01-13 2:13 ` dengke.du 2016-01-13 2:18 ` dengke.du 0 siblings, 2 replies; 12+ messages in thread From: Alexander Kanavin @ 2016-01-08 14:57 UTC (permalink / raw) To: openembedded-core From: Andre McCurdy <armccurdy@gmail.com> Valgrind has been tested on armv5te/qemuarm, so it seems that valgrind's configure check for armv7 is over cautious. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> --- meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb index 0823144..575db35 100644 --- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb +++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb @@ -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__ " -- 2.6.4 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: [PATCH 2/3] valgrind: don't restrict to armv7a 2016-01-08 14:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Alexander Kanavin @ 2016-01-13 2:13 ` dengke.du 2016-01-13 2:18 ` dengke.du 1 sibling, 0 replies; 12+ messages in thread From: dengke.du @ 2016-01-13 2:13 UTC (permalink / raw) To: Alexander Kanavin, openembedded-core [-- Attachment #1: Type: text/plain, Size: 3383 bytes --] 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 On 2016年01月08日 22:57, Alexander Kanavin wrote: > From: Andre McCurdy <armccurdy@gmail.com> > > Valgrind has been tested on armv5te/qemuarm, so it seems > that valgrind's configure check for armv7 is over cautious. > > Signed-off-by: Andre McCurdy <armccurdy@gmail.com> > Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> > --- > meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > index 0823144..575db35 100644 > --- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > +++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > @@ -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__ " [-- Attachment #2: Type: text/html, Size: 4602 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 2/3] valgrind: don't restrict to armv7a 2016-01-08 14:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Alexander Kanavin 2016-01-13 2:13 ` dengke.du @ 2016-01-13 2:18 ` dengke.du 2016-01-13 3:23 ` Andre McCurdy 1 sibling, 1 reply; 12+ messages in thread From: dengke.du @ 2016-01-13 2:18 UTC (permalink / raw) To: Alexander Kanavin, openembedded-core [-- Attachment #1: Type: text/plain, Size: 3383 bytes --] 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 On 2016年01月08日 22:57, Alexander Kanavin wrote: > From: Andre McCurdy <armccurdy@gmail.com> > > Valgrind has been tested on armv5te/qemuarm, so it seems > that valgrind's configure check for armv7 is over cautious. > > Signed-off-by: Andre McCurdy <armccurdy@gmail.com> > Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> > --- > meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > index 0823144..575db35 100644 > --- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > +++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > @@ -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__ " [-- Attachment #2: Type: text/html, Size: 4602 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 2/3] valgrind: don't restrict to armv7a 2016-01-13 2:18 ` dengke.du @ 2016-01-13 3:23 ` Andre McCurdy 2016-01-13 5:00 ` Khem Raj 0 siblings, 1 reply; 12+ messages in thread From: Andre McCurdy @ 2016-01-13 3:23 UTC (permalink / raw) To: dengke.du@windriver.com; +Cc: OE Core mailing list On Tue, Jan 12, 2016 at 6:18 PM, dengke.du@windriver.com <dengke.du@windriver.com> wrote: > 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' 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. > Thanks! > > //dengke > > On 2016年01月08日 22:57, Alexander Kanavin wrote: > > From: Andre McCurdy <armccurdy@gmail.com> > > Valgrind has been tested on armv5te/qemuarm, so it seems > that valgrind's configure check for armv7 is over cautious. > > Signed-off-by: Andre McCurdy <armccurdy@gmail.com> > Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> > --- > meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > index 0823144..575db35 100644 > --- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > +++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb > @@ -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__ " > > > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 2/3] valgrind: don't restrict to armv7a 2016-01-13 3:23 ` Andre McCurdy @ 2016-01-13 5:00 ` Khem Raj 0 siblings, 0 replies; 12+ messages in thread From: Khem Raj @ 2016-01-13 5:00 UTC (permalink / raw) To: Andre McCurdy; +Cc: OE Core mailing list On Tue, Jan 12, 2016 at 7:23 PM, Andre McCurdy <armccurdy@gmail.com> wrote: > On Tue, Jan 12, 2016 at 6:18 PM, dengke.du@windriver.com > <dengke.du@windriver.com> wrote: >> 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. >> | {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' > > 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. > >> Thanks! >> >> //dengke >> >> On 2016年01月08日 22:57, Alexander Kanavin wrote: >> >> From: Andre McCurdy <armccurdy@gmail.com> >> >> Valgrind has been tested on armv5te/qemuarm, so it seems >> that valgrind's configure check for armv7 is over cautious. >> >> Signed-off-by: Andre McCurdy <armccurdy@gmail.com> >> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> >> --- >> meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 8 +++++--- >> 1 file changed, 5 insertions(+), 3 deletions(-) >> >> diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb >> b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb >> index 0823144..575db35 100644 >> --- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb >> +++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb >> @@ -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__ " >> >> >> >> -- >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core >> > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2016-01-13 5:00 UTC | newest] Thread overview: 12+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2015-12-22 23:57 [PATCH 0/3] valgrind fixes Andre McCurdy 2015-12-22 23:57 ` [PATCH 1/3] security_flags.inc: disable -fstack-protector-XXX for valgrind Andre McCurdy 2015-12-22 23:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Andre McCurdy 2016-01-07 21:03 ` Andre McCurdy 2016-01-07 21:39 ` Burton, Ross 2016-01-08 12:43 ` Alexander Kanavin 2015-12-22 23:58 ` [PATCH 3/3] valgrind: include aarch64 in COMPATIBLE_HOST Andre McCurdy -- strict thread matches above, loose matches on Subject: below -- 2016-01-08 14:57 [PATCH 0/3] Valgrind: update to 3.11.0 Alexander Kanavin 2016-01-08 14:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Alexander Kanavin 2016-01-13 2:13 ` dengke.du 2016-01-13 2:18 ` dengke.du 2016-01-13 3:23 ` Andre McCurdy 2016-01-13 5:00 ` Khem Raj
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox