Thanks, closing now.
** Changed in: qemu
Status: Incomplete => Invalid
--
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
Yes, it can be closed.
--
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:
Incomplete
Bug description:
Running "auto
So could we close this QEMU ticket now, or is there still something to
be done from the QEMU side?
** Bug watch removed: Sourceware.org Bugzilla #27543
https://sourceware.org/bugzilla/show_bug.cgi?id=27543
--
You received this bug notification because you are a member of qemu-
devel-ml, which
The patch suggested by Thorsten Glaser glibc Bugzilla #27543 fixes the
issue for me:
> https://sourceware.org/bugzilla/show_bug.cgi?id=27543#c2
** Bug watch added: Sourceware.org Bugzilla #27543
https://sourceware.org/bugzilla/show_bug.cgi?id=27543
--
You received this bug notification becau
We’re looking whether this can be fixed on the glibc side currently.
** Changed in: qemu
Status: Expired => Incomplete
--
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 c
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
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 cra
** Bug watch removed: Sourceware.org Bugzilla #27543
https://sourceware.org/bugzilla/show_bug.cgi?id=27543
--
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-sh
Reported as https://sourceware.org/bugzilla/show_bug.cgi?id=27543
** Bug watch added: Sourceware.org Bugzilla #27543
https://sourceware.org/bugzilla/show_bug.cgi?id=27543
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bug
** Changed in: qemu
Status: Expired => Incomplete
--
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:
Incomplete
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
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 cra
Bug is still pending on git master. Have not pinged the SuperH crew yet.
Will try to do that tomorrow, I'll also ping glibc upstream.
--
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:
au
Did you ever ask the glibc or SuperH experts? Is this bug still pending
in the latest version of QEMU?
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.
We can ask both glibc upstream and some SuperH experts. I'll ask.
--
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:
C
(Edit to note that "that hardware" is an SH7785LCR with an SH7785 CPU.)
--
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 QEM
On that hardware, at least, the user-space visible FPSCR value is indeed
0x00080. Execution of the 'frchg' insn either doesn't trap, or the
trap is caught by the kernel and emulated. I think it is not being
emulated because CONFIG_SH_FPU_EMU is not set.
The comment at the top of arch/sh/kernel
I can provide access to a machine connected to the internet so you can
test it yourself. I'll send you an email.
--
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
I can reproduce this bug, but I'm not sure what QEMU is doing wrong.
Looking at the "SH4 Software Manual", it definitely says that if the
FPSCR.PR bit is 0 then the 'frchg' and 'fschg' instructions should both
trap.
The 'frchg' that autogen is hitting is the one in glibc's "getcontext"
implementa
** Changed in: qemu
Status: New => Confirmed
--
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:
Confirmed
Bug
This is still reproducible on git master:
(sid-sh4-sbuild)root@nofan:/# autogen
Unhandled trap: 0x180
pc=0x7f4da99e sr=0x pr=0x7f3bfc74 fpscr=0x0008
spc=0x ssr=0x gbr=0x7f114320 vbr=0x
sgr=0x dbr=0x delayed_pc=0x7f4da960 fpul=0x0003
r0=0x7ffc
** 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 "auto
20 matches
Mail list logo
