From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] tcg_target_prologue()
Date: Fri, 11 Apr 2008 11:32:10 +0200 [thread overview]
Message-ID: <47FF301A.4010808@bellard.org> (raw)
In-Reply-To: <20080411005722.GA29173@miranda.arrow>
Stuart Brady wrote:
> Hi,
>
> I recently tried using the C version of the TB call in cpu-exec.c,
> "T0 = gen_func();", with HPPA host support. However, I must then save
> the link register, or else it would be overwritten... but if I use
> tcg_target_prologue(), I find that goto_tb sometimes jumps to the
> prologue, but it sometimes jumps past the prologue, instead!
>
> I've fixed the bug[1] that caused me to investigate this, so for the
> time being, I'll continue calling TBs from inline assembly code, but it
> might be nice to spare others the pain of trying tcg_target_prologue()
> and failing. Any thoughts?
The real fix is in the TCG TODO list (global prologue and epilogue). I
will try to implement it ASAP.
Regards,
Fabrice.
prev parent reply other threads:[~2008-04-11 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 0:57 [Qemu-devel] tcg_target_prologue() Stuart Brady
2008-04-11 9:32 ` Fabrice Bellard [this message]
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=47FF301A.4010808@bellard.org \
--to=fabrice@bellard.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).