From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: Alistair Francis <alistair23@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: riscv32 wait() problem, qemu or glibc?
Date: Thu, 17 Sep 2020 00:09:10 +0300 [thread overview]
Message-ID: <9381423.g9G3TJQzCC@farino> (raw)
In-Reply-To: <CAKmqyKPqg4no7DM+z-EdJAAKzta9Mcfn=Fz0DjC5dbSKEtDtCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
> My guess is that somewhere in QEMU the types don't match what RV32 is
> using. It's probably worth printing out the size, alignment and value
> of everything at every stage and see what breaks.
Thanks.
> AFAIK RV32 linux-user mode is pretty much un-tested. So their might be
> all sorts of issues with it unfortunately.
Would you consider qemu system mode more reliable?
I need to prepare some bootable riscv gentoo images eventually anyway. Might
as well try a riscv32 one for comparison then if that is more promising.
--
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 --]
next prev parent reply other threads:[~2020-09-16 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 8:14 riscv32 wait() problem, qemu or glibc? Andreas K. Hüttel
2020-09-15 18:57 ` Andreas K. Hüttel
2020-09-16 15:18 ` Alistair Francis
2020-09-16 21:09 ` Andreas K. Hüttel [this message]
2020-09-16 21:05 ` Alistair Francis
2020-09-17 10:16 ` Andreas K. Hüttel
2020-09-17 14:02 ` Alistair Francis
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=9381423.g9G3TJQzCC@farino \
--to=dilfridge@gentoo.org \
--cc=alistair23@gmail.com \
--cc=libc-alpha@sourceware.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).