-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qemu: update to 9.1.0 #21540
qemu: update to 9.1.0 #21540
Conversation
For the clang64 build failure: https://gitlab.com/qemu-project/qemu/-/issues/2476 |
@lazka @Biswa96 @jeremyd2019 thuth, a core QEMU developer stated:
As I am only contributing to msys2, I ask you the members of msys2 for discussion and decision. |
If upstream doesn't want to fix their struct packing to not depend on gcc_struct there is not much we can do I guess. Not sure, your call. I looked at why they added it in the first place: https://lists.gnu.org/archive/html/qemu-devel/2011-08/msg01877.html |
@mstorsjo are you aware of this limitation? I figured clang has to support both struct packing styles, since it emulates both gcc and msvc frontends, but I guess maybe not both on the same target? |
6cc436c
to
ba269f3
Compare
Yes, I'm aware of this. It's indeed a case where Clang does support both, it just doesn't support the attribute. It does IIRC support |
@lazka @Biswa96 @jeremyd2019 @mstorsjo
.../mingw-w64-qemu/src/build-CLANG64/meson-logs/meson-log.txt:
|
That's too bad - my "default" has been using CLANG64 qemu, generally with whpx but sometimes with tcg for arm64 target. I suppose I'll have to switch to UCRT64 until clang gains support for gcc_struct. |
9e8246c
to
b1f94ba
Compare
@lazka @jeremyd2019 @Biswa96 As already discussed, QEMU packages for clang weren't build, because upstream has introduced a test which currently results in failing clang builds:
|
@lazka @jeremyd2019 @Biswa96 @MehdiChinoune |
see https://wiki.qemu.org/ChangeLog/9.1