From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: qemu-riscv@nongnu.org
Subject: Re: Fwd: riscv32 wait() problem, qemu or glibc?
Date: Sat, 19 Sep 2020 23:41:57 +0300 [thread overview]
Message-ID: <114347864.ZKypZ73Fx5@farino> (raw)
In-Reply-To: <mhng-a7087781-d72b-4824-b649-2535cf70327e@palmerdabbelt-glaptop1>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
Hi Palmer,
> > [1] qemu built from git master, Sep 12, 2020 16:30:37 EEST
> > [2] host kernel is 5.8.8
> > [3] glibc-2.32 with the rv32 patch series backported from master
> > [4] (Gentoo 10.2.0-r1 p2)
> > [5] https://lists.gnu.org/archive/html/bug-bash/2020-09/msg00033.html
>
> I don't see any replies to this, but for some reason I remember having seen
> some. Did this get resolved in some other thread? I'd bet that it's a bug
> in rv32 user-mode emulation, as that's been only lightly used so far.
No resolution yet. The conclusion was also that it's likely a bug in rv32
user-mode emulation, and I put this aside for the moment (to later retry in
softmmu mode).
(the original mail was on qemu-devel and libc-alpha, and there the thread
continued a little bit there, see
https://sourceware.org/pipermail/libc-alpha/2020-September/117563.html )
Best,
Andreas
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, qa, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
prev parent reply other threads:[~2020-09-19 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 16:23 Fwd: riscv32 wait() problem, qemu or glibc? Andreas K. Huettel
2020-09-19 20:33 ` Palmer Dabbelt
2020-09-19 20:41 ` Andreas K. Hüttel [this message]
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=114347864.ZKypZ73Fx5@farino \
--to=dilfridge@gentoo.org \
--cc=palmer@dabbelt.com \
--cc=qemu-riscv@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).