From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1796520] Re: autogen crashes on qemu-sh4-user after 61dedf2af7
Date: Wed, 24 Oct 2018 12:38:05 -0000 [thread overview]
Message-ID: <154038468663.28767.3014440709096802846.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 153886120838.22456.12836438866392888832.malonedeb@gac.canonical.com
** Tags added: linux-user sh4
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1796520
Title:
autogen crashes on qemu-sh4-user after 61dedf2af7
Status in QEMU:
New
Bug description:
Running "autogen --help" crashes on qemu-sh4-user with:
(sid-sh4-sbuild)root@nofan:/# autogen --help
Unhandled trap: 0x180
pc=0xf64dd2de sr=0x00000000 pr=0xf63b9c74 fpscr=0x00080000
spc=0x00000000 ssr=0x00000000 gbr=0xf61102a8 vbr=0x00000000
sgr=0x00000000 dbr=0x00000000 delayed_pc=0xf64dd2a0 fpul=0x00000003
r0=0xf6fc1320 r1=0x00000000 r2=0xffff5dc4 r3=0xf67bfb50
r4=0xf6fc1230 r5=0xf6fc141c r6=0x000003ff r7=0x00000000
r8=0x00000004 r9=0xf63e20bc r10=0xf6fc141c r11=0xf63e28f0
r12=0xf63e2258 r13=0xf63eae1c r14=0x00000804 r15=0xf6fc1220
r16=0x00000000 r17=0x00000000 r18=0x00000000 r19=0x00000000
r20=0x00000000 r21=0x00000000 r22=0x00000000 r23=0x00000000
(sid-sh4-sbuild)root@nofan:/#
Bi-secting found this commit to be the culprit:
61dedf2af79fb5866dc7a0f972093682f2185e17 is the first bad commit
commit 61dedf2af79fb5866dc7a0f972093682f2185e17
Author: Richard Henderson <rth@twiddle.net>
Date: Tue Jul 18 10:02:50 2017 -1000
target/sh4: Add missing FPSCR.PR == 0 checks
Both frchg and fschg require PR == 0, otherwise undefined_operation.
Reviewed-by: Aurelien Jarno <aurelien@aurel32.net>
Signed-off-by: Richard Henderson <rth@twiddle.net>
Message-Id: <20170718200255.31647-26-rth@twiddle.net>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
:040000 040000 980d79b69ae712f23a1e4c56983e97a843153b4a
1024c109f506c7ad57367c63bc8bbbc8a7a36cd7 M target
Reverting 61dedf2af79fb5866dc7a0f972093682f2185e17 fixes the problem
for me.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1796520/+subscriptions
next prev parent reply other threads:[~2018-10-24 13:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 21:26 [Qemu-devel] [Bug 1796520] [NEW] autogen crashes on qemu-sh4-user after 61dedf2af7 John Paul Adrian Glaubitz
2018-10-24 12:38 ` Alex Bennée [this message]
2018-12-14 12:29 ` [Qemu-devel] [Bug 1796520] " John Paul Adrian Glaubitz
2019-04-23 23:19 ` Philippe Mathieu-Daudé
2019-04-23 23:19 ` Philippe Mathieu-Daudé
2019-08-09 14:00 ` Peter Maydell
2019-08-09 14:18 ` John Paul Adrian Glaubitz
2019-08-12 14:36 ` Peter Maydell
2019-08-12 14:48 ` Peter Maydell
2019-08-18 18:07 ` John Paul Adrian Glaubitz
2020-11-23 9:03 ` Thomas Huth
2020-11-26 23:53 ` John Paul Adrian Glaubitz
2021-01-26 4:17 ` Launchpad Bug Tracker
2021-01-26 10:04 ` John Paul Adrian Glaubitz
2021-03-08 12:03 ` John Paul Adrian Glaubitz
2021-05-17 18:59 ` Thomas Huth
2021-05-18 4:17 ` Launchpad Bug Tracker
2021-06-03 13:27 ` Thorsten Glaser
2021-07-21 12:56 ` John Paul Adrian Glaubitz
2021-08-18 13:16 ` Thomas Huth
2021-08-18 13:27 ` John Paul Adrian Glaubitz
2021-08-18 13:45 ` Thomas Huth
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=154038468663.28767.3014440709096802846.launchpad@soybean.canonical.com \
--to=alex.bennee@linaro.org \
--cc=1796520@bugs.launchpad.net \
--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).