From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, John Snow <jsnow@redhat.com>,
stefanha@redhat.com, kbastian@mail.uni-paderborn.de
Subject: [Qemu-devel] [PATCH v2 0/4] configure: clang 3.5.0 build fixes
Date: Wed, 18 Mar 2015 18:43:41 -0400 [thread overview]
Message-ID: <1426718625-24120-1-git-send-email-jsnow@redhat.com> (raw)
QEMU does not compile cleanly under clang 3.5.0. These patches eliminate the
avalanche of warnings and make the build usable.
v2:
- Stole the series from Stefan
- No changes to the -nopie patch, which I think was fine.
- Fixed the -Wno-unknown-attributes patch.
- Added a tricore fix for -Wabsolute-value
- Added a workaround to help suppress ccache warnings
The result is that you *should* be able to use clang 3.5.0 *with* ccache and
-Werror and produce all targets.
John Snow (3):
tricore: remove no-op abs() calls
configure: silence glib unknown attribute __alloc_size__
configure: Add workaround for ccache and clang
Stefan Hajnoczi (1):
configure: handle clang -nopie argument warning
configure | 48 +++++++++++++++++++++++++++++++++++++++++++++-
target-tricore/op_helper.c | 12 ++++++------
2 files changed, 53 insertions(+), 7 deletions(-)
--
2.1.0
next reply other threads:[~2015-03-18 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 22:43 John Snow [this message]
2015-03-18 22:43 ` [Qemu-devel] [PATCH v2 1/4] tricore: remove no-op abs() calls John Snow
2015-03-18 22:51 ` Peter Maydell
2015-03-18 22:55 ` John Snow
2015-03-18 22:43 ` [Qemu-devel] [PATCH v2 2/4] configure: handle clang -nopie argument warning John Snow
2015-03-18 22:43 ` [Qemu-devel] [PATCH v2 3/4] configure: silence glib unknown attribute __alloc_size__ John Snow
2015-03-18 22:55 ` Peter Maydell
2015-03-18 22:43 ` [Qemu-devel] [PATCH v2 4/4] configure: Add workaround for ccache and clang John Snow
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=1426718625-24120-1-git-send-email-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).