From: Aurelien Jarno <aurelien@aurel32.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Blue Swirl" <blauwirbel@gmail.com>,
"Alexander Graf" <agraf@suse.de>,
"Andreas Färber" <afaerber@suse.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/5] softmmu templates: optionally pass CPUState to memory access functions
Date: Sat, 25 Aug 2012 14:53:23 +0200 [thread overview]
Message-ID: <20120825125323.GA17750@hall.aurel32.net> (raw)
In-Reply-To: <CAFEAcA9J0kVvx1qLbhAu0HUXu+HK9N0kXCXQRv3nTBpQVEwCww@mail.gmail.com>
On Sat, Aug 25, 2012 at 12:01:26AM +0100, Peter Maydell wrote:
> On 24 August 2012 19:43, Andreas Färber <afaerber@suse.de> wrote:
> > Depends on what you mean with "disable"? Adding an #error would hurt our
> > arm build just like earlier the ppc build, and I would hope from my last
> > testing that the problems would only affect the AREG0 targets,
> > especially not ARM on ARM (or MIPS on MIPS).
> >
> > Aborting at runtime, only when really unsupported, would seem better.
> >
> > I had taken a look at tcg/arm/ shortly after having fixed ppc (seeing
> > that there was a similar TODO or FIXME) but got distracted by other
> > projects. And your remarks wrt stack sound a bit frightening now. ;)
> > @Peter, have you looked into tcg/arm/ AREG0 support?
>
> Not yet. Why did we commit something that broke half our TCG
> targets and why don't we just back it out for 1.2 ?
>
I haven't tried, but for what I can see in the commit log, it was already
broken in 1.1.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2012-08-25 12:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 22:24 [Qemu-devel] [PATCH 2/5] softmmu templates: optionally pass CPUState to memory access functions Blue Swirl
2012-08-24 15:05 ` Aurelien Jarno
2012-08-24 15:33 ` malc
2012-08-24 15:35 ` malc
2012-08-24 15:52 ` Andreas Färber
2012-08-24 16:26 ` malc
2012-08-24 18:20 ` Andreas Färber
2012-08-24 18:05 ` Aurelien Jarno
2012-08-24 18:43 ` Andreas Färber
2012-08-24 18:53 ` Aurelien Jarno
2012-08-25 9:18 ` Blue Swirl
2012-08-25 12:56 ` Aurelien Jarno
2012-08-24 23:01 ` Peter Maydell
2012-08-25 9:52 ` Blue Swirl
2012-09-20 11:46 ` Alexander Graf
2012-08-25 12:53 ` Aurelien Jarno [this message]
2012-08-25 23:28 ` Peter Maydell
2012-08-26 1:03 ` Peter Maydell
2012-08-25 9:05 ` 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=20120825125323.GA17750@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.com \
--cc=peter.maydell@linaro.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).