qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <damm@opensource.se>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] /* XXX: suppress this hack */
Date: Sun, 10 Oct 2004 20:50:00 +0200	[thread overview]
Message-ID: <1097434199.15737.111.camel@kubu.opensource.se> (raw)
In-Reply-To: <Pine.LNX.4.58.0410102021450.7539@wgmdd8.biozentrum.uni-wuerzburg.de>

Hello there, thanks for the reply!

[snip]

> > I would like to "suppress that hack", ie make sure that AREG4 to AREG11
> > gets defined for i386-softmmu. Someone that knows the code - what needs
> > to be done? Just removing the ifdef does not work for sure. Is it some
> > issue with setjmp()/longjmp()? I'm willing to set aside some hours to
> > fix this if someone who knows points me in the right direction.
> 
> It's all about ABIs: see
> 
> http://www-106.ibm.com/developerworks/linux/library/l-ppc/#h4
> 
> You want all those registers you use to be volatile, i.e. every function
> which wants to use one of those has to make sure that their original
> contents gets restored before returning.

Yeah, registers "r3" to "r12" are "caller save", ie these registers must
be saved before a function is called. But what about "r16" to "r23",
these are currently only used when CONFIG_USER_ONLY is set - I thought
that they were supposed to be saved by the called function prior use,
"callee save". But how does that affect the softmmu code in a bad way
but the user code works? Any ideas?

Thanks!

/ magnus

  reply	other threads:[~2004-10-10 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10 17:59 [Qemu-devel] /* XXX: suppress this hack */ Magnus Damm
2004-10-10 18:23 ` Johannes Schindelin
2004-10-10 18:50   ` Magnus Damm [this message]
2004-10-11 12:51     ` Johannes Schindelin

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=1097434199.15737.111.camel@kubu.opensource.se \
    --to=damm@opensource.se \
    --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).