From: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
To: Vladimir Prus <vladimir@codesourcery.com>, martin.mohring@opensuse.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [6966] SH: Improve movca.l/ocbi emulation.
Date: Fri, 3 Apr 2009 09:35:45 +0200 [thread overview]
Message-ID: <20090403073545.GD14019@edgar.se.axis.com> (raw)
In-Reply-To: <gr46un$rkm$1@ger.gmane.org>
On Fri, Apr 03, 2009 at 09:31:03AM +0400, Vladimir Prus wrote:
> Martin Mohring wrote:
>
> > Hi,
> >
> > could it have been in these changes that i get a linking error for qemu
> > user sh4 on host linux/i586 now?
>
> Probably so -- cpu_sh4_is_cached is defined for system emulation only,
> and helper_movcal is using it unconditionally. I am not sure what is
> the best approach here -- maybe movcal should act like move in user emulation?
>
I committed a specialised is_cached for linux-user that assumes the
entire U0 area is cached.
The runtime link error should be gone now..
Cheers
prev parent reply other threads:[~2009-04-03 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 23:10 [Qemu-devel] [6966] SH: Improve movca.l/ocbi emulation Edgar E. Iglesias
2009-04-02 15:50 ` Martin Mohring
2009-04-03 5:31 ` [Qemu-devel] " Vladimir Prus
2009-04-03 7:35 ` Edgar E. Iglesias [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=20090403073545.GD14019@edgar.se.axis.com \
--to=edgar.iglesias@axis.com \
--cc=martin.mohring@opensuse.org \
--cc=qemu-devel@nongnu.org \
--cc=vladimir@codesourcery.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).