From: Artyom Tarasenko <atar4qemu@gmail.com>
To: Super Bisquit <superbisquit@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] sparc64: fix wrpstate and wrtl on delay slot
Date: Sat, 30 Apr 2011 21:53:10 +0200 [thread overview]
Message-ID: <BANLkTimVDO+94ORWscDEJ-1JPM9T_uU-_g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimRujkOoYyH-fFzeASspN6piK2vGg@mail.gmail.com>
On Sat, Apr 30, 2011 at 9:48 PM, Super Bisquit <superbisquit@gmail.com> wrote:
>
> Just curious, is this for host or guest?
Guest (aka target)
> On Sat, Apr 30, 2011 at 3:32 PM, Igor Kovalenko <igor.v.kovalenko@gmail.com>
> wrote:
>>
>> On Sat, Apr 30, 2011 at 7:42 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
>> > Use TCG local to work around TCG register flush due to a branch.
>> >
>> > Thanks to Artyom Tarasenko, Igor Kovalenko and Aurelien Jarno.
>> >
>> > Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
>> > ---
>> > I analyzed the call tree in target-sparc/translate.c for brcond* usage.
>> > In the following lines, first level function uses brcond* directly,
>> > second level calls the first level etc.
>> >
>>
>> I want to be able to do exhaustive searches as well :)
>> Have you used recently posted gcc save-temps method?
>>
>> --
>> Kind regards,
>> Igor V. Kovalenko
>>
>
>
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next prev parent reply other threads:[~2011-04-30 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 15:42 [Qemu-devel] [PATCH] sparc64: fix wrpstate and wrtl on delay slot Blue Swirl
2011-04-30 19:32 ` Igor Kovalenko
2011-04-30 19:48 ` Super Bisquit
2011-04-30 19:53 ` Artyom Tarasenko [this message]
2011-05-01 7:27 ` Blue Swirl
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=BANLkTimVDO+94ORWscDEJ-1JPM9T_uU-_g@mail.gmail.com \
--to=atar4qemu@gmail.com \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=superbisquit@gmail.com \
/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).