From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Cole Robinson <crobinso@redhat.com>,
Liming Gao <liming.gao@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Yonghong Zhu <yonghong.zhu@intel.com>
Subject: [PATCH 0/3] BaseTools: let the C-language build utils compile with gcc-8
Date: Fri, 2 Mar 2018 19:09:21 +0100 [thread overview]
Message-ID: <20180302180924.4312-1-lersek@redhat.com> (raw)
Repo: https://github.com/lersek/edk2.git
Branch: basetools_gcc8
Once these patches are applied to the build flags and the source code of
the build utilities themselves, OVMF builds fine with gcc-8, using the
GCC5 toolchain settings without any changes.
Regression-tested with gcc-4.8 / x86_64.
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Cole Robinson <crobinso@redhat.com>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Thanks
Laszlo
Laszlo Ersek (3):
BaseTools/header.makefile: add "-Wno-stringop-truncation"
BaseTools/header.makefile: add "-Wno-restrict"
BaseTools/GenVtf: silence false "stringop-overflow" warning with
memcpy()
BaseTools/Source/C/Makefiles/header.makefile | 4 ++--
BaseTools/Source/C/GenVtf/GenVtf.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.14.1.3.gb7cf6e02401b
next reply other threads:[~2018-03-02 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 18:09 Laszlo Ersek [this message]
2018-03-02 18:09 ` [PATCH 1/3] BaseTools/header.makefile: add "-Wno-stringop-truncation" Laszlo Ersek
2018-03-02 18:09 ` [PATCH 2/3] BaseTools/header.makefile: add "-Wno-restrict" Laszlo Ersek
2018-03-02 18:09 ` [PATCH 3/3] BaseTools/GenVtf: silence false "stringop-overflow" warning with memcpy() Laszlo Ersek
2018-03-05 14:13 ` [PATCH 0/3] BaseTools: let the C-language build utils compile with gcc-8 Gao, Liming
2018-03-05 21:41 ` Laszlo Ersek
2018-03-07 6:43 ` Gao, Liming
2018-03-07 9:11 ` Laszlo Ersek
2018-03-07 9:12 ` Ard Biesheuvel
2018-03-07 20:26 ` Laszlo Ersek
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-list 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=20180302180924.4312-1-lersek@redhat.com \
--to=devel@edk2.groups.io \
/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