From: Rob Landley <rob@landley.net>
To: Laurent Vivier <laurent@vivier.eu>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/2] M68k for 2.12 patches
Date: Fri, 30 Mar 2018 11:54:43 -0500 [thread overview]
Message-ID: <d409453e-21c4-c989-c40c-442dcb8f2636@landley.net> (raw)
In-Reply-To: <20180320090813.852-1-laurent@vivier.eu>
On 03/20/2018 04:08 AM, Laurent Vivier wrote:> This series of patches is needed
to fix a problem
> in the m68k translator that can crash QEMU when translation
> cache has too many instructions:
>
> qemu-m68k: tcg/tcg.c:883: tcg_temp_alloc: Assertion `n < 512' failed.
> qemu: uncaught target signal 11 (Segmentation fault) - core dumped
>
> I have reproduced it in linux user mode, with "ghc", and in
> system mode with the debian-installer for unstable distro
> from debian-ports.
If someone wanted to follow along with your "boot linux on qemu-system-m68k"
work on https://github.com/vivier/qemu-m68k, which of the 51 branches should
qemu-system-m68k with like -M q800 or whatever you had working be built from?
Also, "git pull" of the last tree I had from there exploded into a fireball of
automerge conflicts. Is there something I should know?
Rob
next prev parent reply other threads:[~2018-03-30 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 9:08 [Qemu-devel] [PULL 0/2] M68k for 2.12 patches Laurent Vivier
2018-03-20 9:08 ` [Qemu-devel] [PULL 1/2] target/m68k: add DisasContext parameter to gen_extend() Laurent Vivier
2018-03-20 9:08 ` [Qemu-devel] [PULL 2/2] target/m68k: add a mechanism to automatically free TCGv Laurent Vivier
2018-03-20 15:43 ` [Qemu-devel] [PULL 0/2] M68k for 2.12 patches Peter Maydell
2018-03-30 16:54 ` Rob Landley [this message]
2018-03-30 17:00 ` Laurent Vivier
2018-04-02 18:13 ` Rob Landley
2018-04-02 19:05 ` Laurent Vivier
2018-04-02 22:35 ` Rob Landley
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=d409453e-21c4-c989-c40c-442dcb8f2636@landley.net \
--to=rob@landley.net \
--cc=laurent@vivier.eu \
--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).