From: Aurelien Jarno <aurelien@aurel32.net>
To: Richard Henderson <rth@twiddle.net>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Revert "target-sparc: Make cpu_dst local to OP=2 insns"
Date: Sun, 21 Oct 2012 01:17:57 +0200 [thread overview]
Message-ID: <20121020231757.GC23114@hall.aurel32.net> (raw)
In-Reply-To: <50832A54.5020609@twiddle.net>
On Sun, Oct 21, 2012 at 08:48:52AM +1000, Richard Henderson wrote:
> On 2012-10-21 00:48, Aurelien Jarno wrote:
> > I am not sure it is the real problem, but at least the optimization of
> > using the destination register as a temporary is wrong when the
> > instruction might trigger an exception. In that case the result is
> > written to the destination register while it should have not.
> >
> > This reverts commit 5793f2a47e201d251856c7956d6f7907ec0d9f1f.
>
> Which insn might trigger an exception? Most OP=2 insns don't. There's
> divide, but that's done out-of-line, so the assignment to dst does not
> happen before the exception...
Indeed there a are a few one triggering exception, but I looked too
quickly and indeed they do the assignment before. There should be
another problem elsewhere as reverting this patch fixes the issue.
> Is this sparc64? I assume so, since I did test sparc32...
>
Yes it's with a sparc64 kernel. I can reproduce the problem with both a
32 and 64-bit userland, though it happens earlier with a 32-bit
userland.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2012-10-20 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 14:48 [Qemu-devel] [PATCH] Revert "target-sparc: Make cpu_dst local to OP=2 insns" Aurelien Jarno
2012-10-20 22:48 ` Richard Henderson
2012-10-20 23:17 ` Aurelien Jarno [this message]
2012-10-21 21:29 ` Richard Henderson
2012-10-21 22:25 ` Aurelien Jarno
2012-10-22 22:15 ` Aurelien Jarno
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=20121020231757.GC23114@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.