Message ID | 20230202160109.2061994-1-alex.bennee@linaro.org |
---|---|
State | New |
Headers | show |
On Thu, 2 Feb 2023 at 16:01, Alex Bennée <alex.bennee@linaro.org> wrote: > > The following changes since commit 026817fb69414c9d3909d8b1a209f90180d777d6: > > Merge tag 'python-pull-request' of https://gitlab.com/jsnow/qemu into staging (2023-02-01 16:15:56 +0000) > > are available in the Git repository at: > > https://gitlab.com/stsquad/qemu.git tags/pull-jan-omnibus-020223-1 > > for you to fetch changes up to b3ca9646b9a5c44dfd110c5db9b4a8b8497de34e: > > gitlab: cut even more from cross-win64-system build (2023-02-02 13:25:27 +0000) > > ---------------------------------------------------------------- > Testing, docs, semihosting and plugin updates > > - update playbooks for custom runners > - add section timing support to gitlab > - upgrade fedora images to 37 > - purge perl from the build system and deps > - disable unstable tests in CI > - improve intro, emulation and semihosting docs > - semihosting bug fix and O_BINARY default > - add memory-sve test > - fix some races in qht > - improve plugin handling of memory helpers > - optimise plugin hooks > - fix some plugin deadlocks > - reduce win64-cross build time by dropping some targets Applied, thanks. Please update the changelog at https://wiki.qemu.org/ChangeLog/8.0 for any user-visible changes. -- PMM
On 2/2/23 17:01, Alex Bennée wrote: > The following changes since commit 026817fb69414c9d3909d8b1a209f90180d777d6: > > Merge tag 'python-pull-request' of https://gitlab.com/jsnow/qemu into staging (2023-02-01 16:15:56 +0000) > > are available in the Git repository at: > > https://gitlab.com/stsquad/qemu.git tags/pull-jan-omnibus-020223-1 > > for you to fetch changes up to b3ca9646b9a5c44dfd110c5db9b4a8b8497de34e: > > gitlab: cut even more from cross-win64-system build (2023-02-02 13:25:27 +0000) > > ---------------------------------------------------------------- > Testing, docs, semihosting and plugin updates > > - update playbooks for custom runners > - add section timing support to gitlab > - upgrade fedora images to 37 > - purge perl from the build system and deps > - disable unstable tests in CI > - improve intro, emulation and semihosting docs > - semihosting bug fix and O_BINARY default > - add memory-sve test > - fix some races in qht > - improve plugin handling of memory helpers > - optimise plugin hooks > - fix some plugin deadlocks > - reduce win64-cross build time by dropping some targets > > ---------------------------------------------------------------- FTR I'm now seeing this warning on Darwin/Aarch64: C compiler for the host machine: clang (clang 14.0.0 "Apple clang version 14.0.0 (clang-1400.0.29.202)") C linker for the host machine: clang ld64 820.1 Host machine cpu family: aarch64 Host machine cpu: aarch64 ... [1/3253] Linking target tests/plugin/libbb.dylib ld: warning: -undefined dynamic_lookup may not work with chained fixups [2/3253] Linking target tests/plugin/libinsn.dylib ld: warning: -undefined dynamic_lookup may not work with chained fixups [3/3253] Linking target tests/plugin/libmem.dylib ld: warning: -undefined dynamic_lookup may not work with chained fixups [4/3253] Linking target tests/plugin/libsyscall.dylib ld: warning: -undefined dynamic_lookup may not work with chained fixups
On 3/2/23 18:38, Philippe Mathieu-Daudé wrote: > On 2/2/23 17:01, Alex Bennée wrote: >> ---------------------------------------------------------------- >> Testing, docs, semihosting and plugin updates >> ---------------------------------------------------------------- > FTR I'm now seeing this warning on Darwin/Aarch64: > > C compiler for the host machine: clang (clang 14.0.0 "Apple clang > version 14.0.0 (clang-1400.0.29.202)") > C linker for the host machine: clang ld64 820.1 > Host machine cpu family: aarch64 > Host machine cpu: aarch64 > ... > [1/3253] Linking target tests/plugin/libbb.dylib > ld: warning: -undefined dynamic_lookup may not work with chained fixups > [2/3253] Linking target tests/plugin/libinsn.dylib > ld: warning: -undefined dynamic_lookup may not work with chained fixups > [3/3253] Linking target tests/plugin/libmem.dylib > ld: warning: -undefined dynamic_lookup may not work with chained fixups > [4/3253] Linking target tests/plugin/libsyscall.dylib > ld: warning: -undefined dynamic_lookup may not work with chained fixups Googling, someone suggest to use --linkopt=-Wl,-no_fixup_chains: https://github.com/bazelbuild/bazel/issues/16413#issuecomment-1270603343 This doesn't show up on GitLab which uses: C compiler for the host machine: cc (clang 13.1.6 "Apple clang version 13.1.6 (clang-1316.0.21.2.5)") C linker for the host machine: cc ld64 764 Host machine cpu family: aarch64 Host machine cpu: aarch64 I guess I'll just ignore these warnings.
On 2023/02/23 21:59, Philippe Mathieu-Daudé wrote: > On 3/2/23 18:38, Philippe Mathieu-Daudé wrote: >> On 2/2/23 17:01, Alex Bennée wrote: > >>> ---------------------------------------------------------------- >>> Testing, docs, semihosting and plugin updates > >>> ---------------------------------------------------------------- >> FTR I'm now seeing this warning on Darwin/Aarch64: >> >> C compiler for the host machine: clang (clang 14.0.0 "Apple clang >> version 14.0.0 (clang-1400.0.29.202)") >> C linker for the host machine: clang ld64 820.1 >> Host machine cpu family: aarch64 >> Host machine cpu: aarch64 >> ... >> [1/3253] Linking target tests/plugin/libbb.dylib >> ld: warning: -undefined dynamic_lookup may not work with chained fixups >> [2/3253] Linking target tests/plugin/libinsn.dylib >> ld: warning: -undefined dynamic_lookup may not work with chained fixups >> [3/3253] Linking target tests/plugin/libmem.dylib >> ld: warning: -undefined dynamic_lookup may not work with chained fixups >> [4/3253] Linking target tests/plugin/libsyscall.dylib >> ld: warning: -undefined dynamic_lookup may not work with chained fixups > > Googling, someone suggest to use --linkopt=-Wl,-no_fixup_chains: > https://github.com/bazelbuild/bazel/issues/16413#issuecomment-1270603343 > > This doesn't show up on GitLab which uses: > > C compiler for the host machine: cc (clang 13.1.6 "Apple clang version > 13.1.6 (clang-1316.0.21.2.5)") > C linker for the host machine: cc ld64 764 > Host machine cpu family: aarch64 > Host machine cpu: aarch64 > > I guess I'll just ignore these warnings. I think this problem is tracked at: https://gitlab.com/qemu-project/qemu/-/issues/1244 It is caused by linker flags Meson adds. For Meson, it is tracked at: https://github.com/mesonbuild/meson/issues/10894
On 24/2/23 05:51, Akihiko Odaki wrote: > On 2023/02/23 21:59, Philippe Mathieu-Daudé wrote: >> On 3/2/23 18:38, Philippe Mathieu-Daudé wrote: >>> On 2/2/23 17:01, Alex Bennée wrote: >> >>>> ---------------------------------------------------------------- >>>> Testing, docs, semihosting and plugin updates >> >>>> ---------------------------------------------------------------- >>> FTR I'm now seeing this warning on Darwin/Aarch64: >>> >>> C compiler for the host machine: clang (clang 14.0.0 "Apple clang >>> version 14.0.0 (clang-1400.0.29.202)") >>> C linker for the host machine: clang ld64 820.1 >>> Host machine cpu family: aarch64 >>> Host machine cpu: aarch64 >>> ... >>> [1/3253] Linking target tests/plugin/libbb.dylib >>> ld: warning: -undefined dynamic_lookup may not work with chained fixups >>> [2/3253] Linking target tests/plugin/libinsn.dylib >>> ld: warning: -undefined dynamic_lookup may not work with chained fixups >>> [3/3253] Linking target tests/plugin/libmem.dylib >>> ld: warning: -undefined dynamic_lookup may not work with chained fixups >>> [4/3253] Linking target tests/plugin/libsyscall.dylib >>> ld: warning: -undefined dynamic_lookup may not work with chained fixups >> >> Googling, someone suggest to use --linkopt=-Wl,-no_fixup_chains: >> https://github.com/bazelbuild/bazel/issues/16413#issuecomment-1270603343 >> >> This doesn't show up on GitLab which uses: >> >> C compiler for the host machine: cc (clang 13.1.6 "Apple clang version >> 13.1.6 (clang-1316.0.21.2.5)") >> C linker for the host machine: cc ld64 764 >> Host machine cpu family: aarch64 >> Host machine cpu: aarch64 >> >> I guess I'll just ignore these warnings. > > I think this problem is tracked at: > https://gitlab.com/qemu-project/qemu/-/issues/1244 > > It is caused by linker flags Meson adds. For Meson, it is tracked at: > https://github.com/mesonbuild/meson/issues/10894 Indeed. Thank you Akihiko :)