From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Mahmoud Mandour" <ma.mandourr@gmail.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"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: Mon, 13 Jan 2025 21:19:03 +0000 [thread overview]
Message-ID: <87y0zejttk.fsf@draig.linaro.org> (raw)
In-Reply-To: <6adc2994-e762-4923-9033-54efe165aaea@linaro.org> (Pierrick Bouvier's message of "Mon, 13 Jan 2025 12:17:27 -0800")
Pierrick Bouvier <pierrick.bouvier@linaro.org> writes:
> On 1/12/25 22:26, Thomas Huth wrote:
>> On 11/01/2025 16.47, Philippe Mathieu-Daudé wrote:
>>> On 10/1/25 21:37, Pierrick Bouvier wrote:
>>>> On 1/10/25 12:33, Pierrick Bouvier wrote:
>>>>> 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(-)
>>>>>
>>>>
>>>> It would be nice if a maintainer could pull this, so we can get this
>>>> merged upstream.
>>>
>>> That'd be Thomas or Alex I suppose.
>> This touches plugins, so I think it should go through Alex' tree?
>> Thomas
>>
>
> It's touching plugins, but it does a system wide change as well (which
> is the most important part).
>
> It's not really important who merges this, but it would be better if
> the series could be pulled as a whole, instead of breaking it into
> multiple subsystems.
I'll look at it tomorrow when going through my maintainer queue.
>
> Thanks,
> Pierrick
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-01-13 21:20 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 [this message]
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
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=87y0zejttk.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.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=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--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).