On Fri, 2023-01-20 at 10:41 +0100, Thomas Huth wrote:
On 16/01/2023 23.36, Richard Henderson wrote:
The following changes since commit
fb7e7990342e59cf67dbd895c1a1e3fb1741df7a:
tests/qtest/qom-test: Do not print tested properties by default
(2023-01-16 15:00:57 +0000)
are available in the Git repository at:
https://gitlab.com/rth7680/qemu.git tags/pull-tcg-20230116
for you to fetch changes up to
61710a7e23a63546da0071ea32adb96476fa5d07:
accel/tcg: Split out cpu_exec_{setjmp,loop} (2023-01-16 10:14:12
-1000)
----------------------------------------------------------------
- Reorg cpu_tb_exec around setjmp.
- Use __attribute__((target)) for buffer_is_zero.
- Add perfmap and jitdump for perf support.
----------------------------------------------------------------
Ilya Leoshkevich (3):
linux-user: Clean up when exiting due to a signal
accel/tcg: Add debuginfo support
tcg: add perfmap and jitdump
Richard Henderson (2):
util/bufferiszero: Use __attribute__((target)) for
avx2/avx512
accel/tcg: Split out cpu_exec_{setjmp,loop}
Hi Richard, hi Ilya,
with the recent QEMU master branch (commit 701ed34), I'm now seeing
failures
in Travis:
https://app.travis-ci.com/github/huth/qemu/jobs/593786529#L14411
Everything was still fine a couple of days ago (commit fb7e799):
https://app.travis-ci.com/github/huth/qemu/builds/259755664
... so it seems this is likely related to this pull request. Could
you
please have a look?
Thanks,
Thomas
I would expect this to be (temporarily) fixed by [1], but we probably
don't set GITLAB_CI in Travis. Would it make sense to set it? It looks
as if this variable is currently used only to skip certain tests.
If not, then maybe split it into QEMU_CI, GITLAB_CI and TRAVIS_CI?
https://lists.gnu.org/archive/html/qemu-devel/2023-01/msg04438.html