All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: "Thomas Huth" <thuth@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: Supporting clang on windows
Date: Mon, 25 Nov 2024 08:48:09 -0800	[thread overview]
Message-ID: <d02f2221-ffa6-4232-bfcf-a19deee6d1ac@linaro.org> (raw)
In-Reply-To: <05108195-009e-4d06-bc79-065b1e3432ed@redhat.com>

Thanks everyone for your valuable feedback on this, and taking time to 
give more rationale about the previous position you had.

On 11/25/24 03:19, Thomas Huth wrote:
> 
> So fine for me if we allow compiling with Clang on Windows now, but we
> should make sure to avoid that those problems are sneaking in again. So
> Pierrick, please provide a patch to docs/devel/style.rst to say that we
> disallow bitfields in packed structs in future contributions. Then I think
> it's ok to remove the gcc_struct from QEMU_PACKED. (Just my 2 cents, of course)
> 
>    Thomas
> 

I just compared windows binaries with/without gcc_struct, and as Thomas 
found for qemu linux binaries using pahole, there is no difference with 
or without gcc_struct, so the attribute is unused now.

In case you want to check that by yourself, I uploaded binaries and 
dwarf info on this repo:
https://github.com/pbo-linaro/qemu_packed_structs
(gcc_attribute has gcc_struct binaries, gcc_no_attribute_no_option has 
binaries without it).

Before sending the a series removing gcc_struct and editing the 
documentation, do we all agree here it's the right move forward?
If yes, should we apply this to 9.2 release?

Thanks,
Pierrick


  reply	other threads:[~2024-11-25 16:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-24  0:21 Supporting clang on windows Pierrick Bouvier
2024-11-24 12:10 ` Paolo Bonzini
2024-11-24 20:23   ` Pierrick Bouvier
2024-11-25  7:00     ` Paolo Bonzini
2024-11-25  9:34       ` Daniel P. Berrangé
2024-11-25  9:39         ` Paolo Bonzini
2024-11-25 10:42           ` Peter Maydell
2024-11-25 11:19           ` Thomas Huth
2024-11-25 16:48             ` Pierrick Bouvier [this message]
2024-11-25 17:05               ` Peter Maydell
2024-11-25 21:47                 ` Pierrick Bouvier
2024-11-26 21:24                   ` Pierrick Bouvier
2024-11-25 16:55       ` Pierrick Bouvier
2024-11-25  7:15     ` Thomas Huth
2024-11-24 12:28 ` Philippe Mathieu-Daudé
2024-11-24 20:24   ` Pierrick Bouvier
2024-11-25  6:31   ` Thomas Huth
2024-11-25 14:04 ` Richard Henderson
2024-11-25 16:19   ` Pierrick Bouvier

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=d02f2221-ffa6-4232-bfcf-a19deee6d1ac@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.