From: Torbjorn Granlund <tg@gmplib.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1156313] [NEW] X86-64 flags handling broken
Date: Mon, 25 Mar 2013 15:06:18 +0100 [thread overview]
Message-ID: <86vc8fmv51.fsf@shell.gmplib.org> (raw)
In-Reply-To: <86r4j8960v.fsf@shell.gmplib.org> (Torbjorn Granlund's message of "Thu\, 21 Mar 2013 15\:33\:36 +0100")
After the latest patch of Richard's, qemu-system-x86_64 now runs
GNU/Linux properly. The denorm problem is gone, and there seem to be no
(or at least much fewer) spurious segfaults.
This ends a multi-month period of qemu-system-x86_64 instability.
Still qemu-system-mips64, qemu-system-mips64el, and qemu-system-arm
give spurious errors. The former two have never (at least not the last
3-4 years) been able to run a GMP
configure && make && make check
reliably. No regression there, just maintained buggyness...
--
Torbjörn
next prev parent reply other threads:[~2013-03-25 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 19:34 [Qemu-devel] [Bug 1156313] [NEW] X86-64 flags handling broken Torbjorn Granlund
2013-03-19 18:17 ` Richard Henderson
2013-03-21 14:33 ` Torbjorn Granlund
2013-03-25 14:06 ` Torbjorn Granlund [this message]
2013-03-25 14:08 ` Peter Maydell
2013-03-25 16:09 ` Torbjorn Granlund
2017-11-07 19:10 ` [Qemu-devel] [Bug 1156313] " Peter Maydell
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=86vc8fmv51.fsf@shell.gmplib.org \
--to=tg@gmplib.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).