From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Brian Cain <brian.cain@oss.qualcomm.com>,
Stefan Weil <stefan.weil@weilnetz.de>,
qemu-devel@nongnu.org
Cc: "Mahmoud Mandour" <ma.mandourr@gmail.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Alexandre Iooss" <erdnaxe@crans.org>
Subject: Re: [PATCH v4 0/3] Enable clang build on Windows
Date: Tue, 18 Feb 2025 08:22:14 -0800 [thread overview]
Message-ID: <71254e1d-3e17-4082-968f-db7fe6cea590@linaro.org> (raw)
In-Reply-To: <4e788add-ee40-4d98-b065-6745e6e2fce5@oss.qualcomm.com>
Hi Brian,
On 2/17/25 20:11, Brian Cain wrote:
>
> On 1/11/2025 4:08 PM, Stefan Weil via wrote:
>> Am 10.01.25 um 21:33 schrieb Pierrick Bouvier:
>>> For now, it was only possible to build plugins using GCC on Windows.
>>> However,
>>> windows-aarch64 only supports Clang.
>>> This biggest roadblock was to get rid of gcc_struct attribute, which
>>> is not
>>> supported by Clang. After investigation, we proved it was safe to
>>> drop it.
>>>
>>> Built and tested on Windows (all msys env)/Linux/MacOS for x86_64 and
>>> aarch64
>>> hosts.
>>>
>>> v1 contained warning fixes and various bits that have been upstreamed
>>> already.
>>> The only bits left in this series are the gcc_struct removal, and
>>> fixing the
>>> plugins build with clang.
>>>
>>> This series is for 10.0, as we decided to not include the gcc_struct
>>> removal is
>>> 9.2 release.
>>>
>>> All patches are now reviewed, so this series can be pulled. I'll
>>> report that to
>>> MSYS2 too, so we can enable clang environments for QEMU.
>>>
>>> v1:
>>> https://patchew.org/QEMU/20241031040426.772604-1-pierrick.bouvier@linaro.org/
>>>
>>> v2:
>>> - drop attribute gcc_struct instead of using -mno-ms-bitfields option
>>> - add a section about bitfields in documentation
>>>
>>> v3:
>>> - explain why gcc_struct attribute matters in packed structs in
>>> commit message
>>> - reword the bitfields documentation with suggestions given
>>>
>>> v4:
>>> - edit for bitfields doc requested by Philippe
>>>
>>> Pierrick Bouvier (3):
>>> win32: remove usage of attribute gcc_struct
>>> docs/devel/style: add a section about bitfield, and disallow them for
>>> packed structures
>>> plugins: enable linking with clang/lld
>>>
>>> docs/devel/style.rst | 20 +++++++++++++++++++
>>> meson.build | 6 +++---
>>> include/qemu/compiler.h | 7 +------
>>> scripts/cocci-macro-file.h | 6 +-----
>>> subprojects/libvhost-user/libvhost-user.h | 6 +-----
>>> contrib/plugins/meson.build | 2 +-
>>> plugins/meson.build | 24 +++++++++++++++++++----
>>> tests/tcg/plugins/meson.build | 3 +--
>>> 8 files changed, 48 insertions(+), 26 deletions(-)
>>
>> This nice series allows building QEMU for Windows with the LLVM cross
>> compiler on my ARM64 machine, so you can add
>
> Is this toolchain available publicly or did you build it yourself? It
> would be handy if there were a linux x86_64 hosted cross-toolchain that
> can target Windows-aarch64. Or linux aarch64 hosted would be pretty
> good, too.
>
At the moment, the only open source toolchain supporting windows-arm64
is llvm-mingw (https://github.com/mstorsjo/llvm-mingw).
There is some progress on gcc, but it is not yet fully upstream.
MSYS2 uses llvm-mingw for windows-arm64 environment.
On my side, I used a windows-arm64 machine with MSYS2 native environment.
It would be handy to cross compile, and the problem is not really QEMU
itself, but to cross compile all the dependencies.
For x86_64, we use fedora, which provides convenient precompiled mingw
packages for dependencies.
It's definitely not impossible to do the same for windows-arm64, but it
just takes much more effort.
> Is there an MSYS2 or other distributor that provides windows-aarch64
> builds of the glib and other library dependencies?
>
MSYS2 does, but it's complicated to download packages by hand if it's
your idea. Better to cross compile it.
Regards,
Pierrick
>>
>> Tested-by: Stefan Weil <sw@weilnetz.de>
>>
>> I only needed a trivial additional fix in scripts/nsis.py for `make
>> installer` because the usual GNU objdump and the LLVM objdump (or the
>> cross x86_64-w64-mingw32-objdump in my test) produce slightly
>> different output (indentation with \t, indentation with four spaces).
>> I'll prepare a patch which eliminates the need for objdump, so no
>> intermediate fix is needed for this.
>>
>> Stefan W.
>>
next prev parent reply other threads:[~2025-02-18 16:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 20:33 [PATCH v4 0/3] Enable clang build on Windows Pierrick Bouvier
2025-01-10 20:33 ` [PATCH v4 1/3] win32: remove usage of attribute gcc_struct Pierrick Bouvier
2025-01-13 23:38 ` Michael S. Tsirkin
2025-01-10 20:34 ` [PATCH v4 2/3] docs/devel/style: add a section about bitfield, and disallow them for packed structures Pierrick Bouvier
2025-01-10 20:34 ` [PATCH v4 3/3] plugins: enable linking with clang/lld Pierrick Bouvier
2025-01-10 20:37 ` [PATCH v4 0/3] Enable clang build on Windows Pierrick Bouvier
2025-01-11 15:47 ` Philippe Mathieu-Daudé
2025-01-12 18:03 ` Philippe Mathieu-Daudé
2025-01-13 6:26 ` Thomas Huth
2025-01-13 20:17 ` Pierrick Bouvier
2025-01-13 21:19 ` Alex Bennée
2025-01-13 21:22 ` Pierrick Bouvier
2025-01-11 22:08 ` Stefan Weil via
2025-01-12 17:54 ` Pierrick Bouvier
2025-02-18 4:11 ` Brian Cain
2025-02-18 16:22 ` Pierrick Bouvier [this message]
2025-02-18 16:26 ` Daniel P. Berrangé
2025-02-18 20:59 ` Stefan Weil via
2025-02-18 23:17 ` Pierrick Bouvier
2025-02-19 6:39 ` Stefan Weil via
2025-02-19 7:01 ` Pierrick Bouvier
2025-02-19 7:38 ` Stefan Weil via
2025-01-14 8:20 ` Alex Bennée
2025-01-14 8:35 ` Philippe Mathieu-Daudé
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=71254e1d-3e17-4082-968f-db7fe6cea590@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=brian.cain@oss.qualcomm.com \
--cc=erdnaxe@crans.org \
--cc=ma.mandourr@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefan.weil@weilnetz.de \
--cc=thuth@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).