qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Peter Maydell" <peter.maydell@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/8] tcg + linux-user patch queue
Date: Tue, 23 Jan 2024 08:02:21 +1000	[thread overview]
Message-ID: <d9bee29b-2317-41be-87c6-55fc42f9804e@linaro.org> (raw)
In-Reply-To: <CAFEAcA84d+mq85kae=yiwNvg1Ja=SKch00mocuNok1VghiYozQ@mail.gmail.com>

On 1/23/24 01:26, Peter Maydell wrote:
> On Sun, 21 Jan 2024 at 00:22, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> The following changes since commit 3f2a357b95845ea0bf7463eff6661e43b97d1afc:
>>
>>    Merge tag 'hw-cpus-20240119' of https://github.com/philmd/qemu into staging (2024-01-19 11:39:38 +0000)
>>
>> are available in the Git repository at:
>>
>>    https://gitlab.com/rth7680/qemu.git tags/pull-tcg-20240121
>>
>> for you to fetch changes up to 1d5e32e3198d2d8fd2342c8f7f8e0875aeff49c5:
>>
>>    linux-user/elfload: check PR_GET_DUMPABLE before creating coredump (2024-01-21 10:25:07 +1100)
>>
>> ----------------------------------------------------------------
>> tcg/s390x: Fix encoding of VRIc, VRSa, VRSc insns
>> tcg: Clean up error paths in alloc_code_gen_buffer_splitwx_memfd
>> linux-user/riscv: Adjust vdso signal frame cfa offsets
>> linux-user: Fixed cpu restore with pc 0 on SIGBUS
>>
>> ----------------------------------------------------------------
> 
> The new chacha test seems to consistently segfault on aarch64 host:
> 
> https://gitlab.com/qemu-project/qemu/-/jobs/5979230595
> https://gitlab.com/qemu-project/qemu/-/jobs/5978381815
> https://gitlab.com/qemu-project/qemu/-/jobs/5982075408

Oh dear.  It seems to be a problem with the aarch64 cross-compiler for s390x.
If I use a binary created on an s390x or x86_64 host, it works.

Unless someone has a better idea, I'll drop the testcase for now.


r~


  reply	other threads:[~2024-01-22 22:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21  0:20 [PULL 0/8] tcg + linux-user patch queue Richard Henderson
2024-01-21  0:20 ` [PULL 1/8] tcg: Remove unreachable code Richard Henderson
2024-01-21  0:20 ` [PULL 2/8] tcg: Make the cleanup-on-error path unique Richard Henderson
2024-01-21  0:20 ` [PULL 3/8] linux-user: Fixed cpu restore with pc 0 on SIGBUS Richard Henderson
2024-01-21  0:20 ` [PULL 4/8] tcg/s390x: Fix encoding of VRIc, VRSa, VRSc insns Richard Henderson
2024-01-21  0:20 ` [PULL 5/8] tests/tcg/s390x: Import linux tools/testing/crypto/chacha20-s390 Richard Henderson
2024-01-21  0:20 ` [PULL 6/8] linux-user/riscv: Adjust vdso signal frame cfa offsets Richard Henderson
2024-01-21  0:20 ` [PULL 7/8] linux-user/elfload: test return value of getrlimit Richard Henderson
2024-01-21  0:20 ` [PULL 8/8] linux-user/elfload: check PR_GET_DUMPABLE before creating coredump Richard Henderson
2024-01-21  7:33 ` [PULL 0/8] tcg + linux-user patch queue Michael Tokarev
2024-01-22 15:26 ` Peter Maydell
2024-01-22 22:02   ` Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-12 18:41 Richard Henderson
2024-03-13 12:36 ` Peter Maydell

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=d9bee29b-2317-41be-87c6-55fc42f9804e@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).