From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/3] valgrind cleanup + fix for armv7a without vfp/neon
Date: Tue, 19 Jan 2016 18:47:48 -0800 [thread overview]
Message-ID: <1453258071-22847-1-git-send-email-armccurdy@gmail.com> (raw)
v2: fix issue with intdiv test if TUNE_CCARGS sets -march instead of -mcpu
Andre McCurdy (3):
valgrind: let valgrind determine its own optimisation flags
valgrind: re-enable ARM intdiv and vcvt_fixed_float_VFP tests
valgrind: avoid neon for targets which don't support it
...d-neon-for-targets-which-don-t-support-it.patch | 33 +++++++++++
.../valgrind/remove-arm-variant-specific.patch | 66 ----------------------
...opriate-march-mcpu-mfpu-for-ARM-test-apps.patch | 44 +++++++++++++++
meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 12 ++--
4 files changed, 85 insertions(+), 70 deletions(-)
create mode 100644 meta/recipes-devtools/valgrind/valgrind/avoid-neon-for-targets-which-don-t-support-it.patch
delete mode 100644 meta/recipes-devtools/valgrind/valgrind/remove-arm-variant-specific.patch
create mode 100644 meta/recipes-devtools/valgrind/valgrind/use-appropriate-march-mcpu-mfpu-for-ARM-test-apps.patch
--
1.9.1
next reply other threads:[~2016-01-20 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 2:47 Andre McCurdy [this message]
2016-01-20 2:47 ` [PATCH v2 1/3] valgrind: let valgrind determine its own optimisation flags Andre McCurdy
2016-01-20 2:47 ` [PATCH v2 2/3] valgrind: re-enable ARM intdiv and vcvt_fixed_float_VFP tests Andre McCurdy
2016-01-20 3:00 ` Rongqing Li
2016-01-20 2:47 ` [PATCH v2 3/3] valgrind: avoid neon for targets which don't support it Andre McCurdy
2016-01-20 3:00 ` Rongqing Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1453258071-22847-1-git-send-email-armccurdy@gmail.com \
--to=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.