From: Joe Slater <jslater@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] valgrind - gcc7 and powerpc64
Date: Thu, 13 Jul 2017 17:24:20 -0700 [thread overview]
Message-ID: <1499991861-19044-1-git-send-email-jslater@windriver.com> (raw)
This probably could do no harm since the actual code generated does not
seem to have changed between gcc6 and gcc7, and is not affected by this patch
except that without it, valgrind ppc64 won't compile.
There must also be a gcc7 bug, since if it is ok to clobber r2 for ppc32 it
is unlikely it is not ok for ppc64.
Joe Slater (1):
valgrind: allow version 3.12 to build under gcc7
.../valgrind/valgrind/wait-for-3.13.patch | 40 ++++++++++++++++++++++
meta/recipes-devtools/valgrind/valgrind_3.12.0.bb | 3 ++
2 files changed, 43 insertions(+)
create mode 100644 meta/recipes-devtools/valgrind/valgrind/wait-for-3.13.patch
--
2.7.4
next reply other threads:[~2017-07-14 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 0:24 Joe Slater [this message]
2017-07-14 0:24 ` [PATCH 1/1] valgrind: allow version 3.12 to build under gcc7 Joe Slater
2017-07-14 1:40 ` Khem Raj
2017-07-14 8:42 ` Sören Brinkmann
2017-07-14 0:31 ` ✗ patchtest: failure for valgrind - gcc7 and powerpc64 Patchwork
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=1499991861-19044-1-git-send-email-jslater@windriver.com \
--to=jslater@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox