From: John Thomson <lists@johnthomson.fastmail.com.au>
To: Jason Andryuk <jandryuk@gmail.com>, Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: staging GCC 8.1.0 build warnings
Date: Tue, 15 May 2018 11:42:08 +1000 [thread overview]
Message-ID: <1526348528.3519185.1372169584.0119D195@webmail.messagingengine.com> (raw)
In-Reply-To: <CAKf6xpsu__xS5urkF-GNTZCxTE3VGqNZFinj6EB0eekqsGHi1A@mail.gmail.com>
On Tue, 15 May 2018, at 04:20, Jason Andryuk wrote:
> > On Thu, May 10, 2018 at 09:38:26AM +1000, John Thomson wrote:
> >> /build/xen-git/src/xen/stubdom/tpm_emulator-x86_64/tpm/tpm_deprecated.c:437:7: error: 'memcmp' reading 20 bytes from a region of size 8 [-Werror=stringop-overflow=]
> >> if (memcmp(&b1, &newAuthLink, sizeof(TPM_HMAC))) {
> >> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> A fix is proposed upstream:
> https://github.com/PeterHuewe/tpm-emulator/pull/30/commits/910c43273c9f3373f93c2e8b8b0929d89fdcead6
Thank you, I had completely missed that.
The qemu-xen patches to fix gcc-8 warnings are in qemu-xen staging, but they are not yet in master.
This will need a new tag for the next 4.11rc when they come through?
> >> For IPXE, one of these patches:
> >> https://build.opensuse.org/package/view_file/openSUSE:Factory/qemu/ipxe-efi-guard-strncpy-with-gcc-warning-ignore-pragma.patch?expand=1
For IPXE I needed the [build] Use -no-pie on newer versions of gcc patch, as well as the guard-strncpy patch.
https://github.com/ipxe/ipxe/commit/7c395b0e21806b946fe944a27fc273407f357ea1
Cheers,
--
John Thomson
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-05-15 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 23:38 staging GCC 8.1.0 build warnings John Thomson
2018-05-14 17:03 ` Wei Liu
2018-05-14 18:20 ` Jason Andryuk
2018-05-15 1:42 ` John Thomson [this message]
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=1526348528.3519185.1372169584.0119D195@webmail.messagingengine.com \
--to=lists@johnthomson.fastmail.com.au \
--cc=jandryuk@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).