From: Cole Robinson <crobinso@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: clang build error on i686
Date: Sat, 3 Jul 2021 10:34:56 -0400 [thread overview]
Message-ID: <abc8f7fe-2afe-0f5d-d391-6277db6e6f42@redhat.com> (raw)
Hi, I'm hitting build errors with clang on i686 userspace on x86_64
kernel. Affects both qemu 6.0.0 and qemu.git, tested with fedora
clang-12.0.1~rc3-1.fc35.i686.
Full build log from the 6.0.0 build:
https://gist.githubusercontent.com/crobinso/7b1206044eac7326490b2adce829e861/raw/9dddef968051fd6383ba7adb9e595081ad4f8fa4/gistfile1.txt
Lots of errors like:
/usr/bin/ld: libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o: in
function `helper_atomic_cmpxchgq_le_mmu':
/builddir/build/BUILD/qemu-6.0.0/accel/tcg/atomic_template.h:86:
undefined reference to `__atomic_compare_exchange_8'
/usr/bin/ld: libqemu-aarch64-softmmu.fa.p/accel_tcg_cputlb.c.o: in
function `helper_atomic_xchgq_le_mmu':
/builddir/build/BUILD/qemu-6.0.0/accel/tcg/atomic_template.h:134:
undefined reference to `__atomic_exchange_8'
Also warnings like:
/builddir/build/BUILD/qemu-6.0.0/include/qemu/stats64.h:58:21: warning:
misaligned atomic operation may incur significant performance penalty;
the expected alignment (8 bytes) exceeds the actual alignment (4 bytes)
[-Watomic-alignment]
uint64_t orig = qatomic_read__nocheck(&s->value);
^
/builddir/build/BUILD/qemu-6.0.0/include/qemu/atomic.h:129:5: note:
expanded from macro 'qatomic_read__nocheck'
__atomic_load_n(ptr, __ATOMIC_RELAXED)
Search the log for __atomic for other hits.
Thanks,
Cole
next reply other threads:[~2021-07-03 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 14:34 Cole Robinson [this message]
2021-07-03 16:20 ` clang build error on i686 Philippe Mathieu-Daudé
2021-07-03 16:27 ` Philippe Mathieu-Daudé
2021-07-03 16:25 ` Philippe Mathieu-Daudé
2021-07-03 17:45 ` Peter Maydell
2021-07-11 15:17 ` Richard Henderson
2021-07-11 17:50 ` Peter Maydell
2021-07-12 16:10 ` Richard Henderson
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=abc8f7fe-2afe-0f5d-d391-6277db6e6f42@redhat.com \
--to=crobinso@redhat.com \
--cc=qemu-devel@nongnu.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).