From: Richard Henderson <rth@twiddle.net>
To: Laurent Vivier <laurent@vivier.eu>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] target-m68k patches
Date: Mon, 7 Nov 2016 13:08:12 +0100 [thread overview]
Message-ID: <cb43dc45-d4ee-901e-108c-b68b7eb5e927@twiddle.net> (raw)
In-Reply-To: <c991dc75-0231-3eff-2613-46454f977c5c@vivier.eu>
On 11/06/2016 08:52 PM, Laurent Vivier wrote:
>> Richard Henderson (4):
>> target-m68k: Do not cpu_abort on undefined insns
>> target-m68k: Inline shifts
>> target-m68k: Implement bitfield ops for registers
>> target-m68k: Implement bitfield ops for memory
>
> There is something wrong with the bitfield patches, because when I use
> them instead of the version I use usually I'm not able to boot a
> container with qemu-m68k (SEGFAULT).
Ah, too bad. I was testing with the linux-user-0.3 busybox, but we don't yet
implement enough to actually execute it. So the testing consisted of maybe 3
or 4 such insns until I reach the fmovemx. ;-)
Can you tell if the breakage is limited to the memory patch, or if the register
patch is also broken?
r~
next prev parent reply other threads:[~2016-11-07 12:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 6:18 [Qemu-devel] [PATCH 0/5] target-m68k patches Richard Henderson
2016-11-06 6:18 ` [Qemu-devel] [PATCH 1/5] target-m68k: implement 680x0 movem Richard Henderson
2016-11-06 16:52 ` Laurent Vivier
2016-11-06 6:18 ` [Qemu-devel] [PATCH 2/5] target-m68k: Do not cpu_abort on undefined insns Richard Henderson
2016-11-06 16:53 ` Laurent Vivier
2016-11-06 6:18 ` [Qemu-devel] [PATCH 3/5] target-m68k: Inline shifts Richard Henderson
2016-11-06 6:18 ` [Qemu-devel] [PATCH 4/5] target-m68k: Implement bitfield ops for registers Richard Henderson
2016-11-06 6:18 ` [Qemu-devel] [PATCH 5/5] target-m68k: Implement bitfield ops for memory Richard Henderson
2016-11-06 19:52 ` [Qemu-devel] [PATCH 0/5] target-m68k patches Laurent Vivier
2016-11-07 12:08 ` Richard Henderson [this message]
2016-11-07 12:24 ` Laurent Vivier
2016-11-07 13:12 ` Peter Maydell
2016-11-07 13:44 ` Laurent Vivier
2016-11-07 13:50 ` Peter Maydell
2016-11-07 14:00 ` Laurent Vivier
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=cb43dc45-d4ee-901e-108c-b68b7eb5e927@twiddle.net \
--to=rth@twiddle.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).