All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Sparc port
Date: Sun, 08 Jun 2003 12:10:22 +0200	[thread overview]
Message-ID: <3EE30B8E.5070600@free.fr> (raw)


I am now trying to make the Sparc port work again. I added a sparc 
disassembler so that debugging is easier.

In order to support direct block chaining, it is necessary that no 
prologue or epilogue are added in the generated code. It should be easy 
to do by moving the add/sub sp/fp in the call code in exec-i386.c.

Moreover, the 'restore' used in exec-i386.c in cpu_loop_exit() is not 
safe because we cannot be sure that there was exactly one call level.

I have two ideas :

1) We use -mflat for exec-i386.c and helper-i386.c but not for op-i386.c 
to avoid gcc bugs. Now that op-i386.c only contains opcodes, the code 
inside should almost look like '-mflat' code.

2) We can patch cpu_exit_loop() by doing the right number of restores 
(maybe a single longjmp would suffice as l0...l7 are still saved.


Another more general idea for all archs is to call the generated code 
with a 'jump' instead of doing a call. It would be marginaly more 
complicated and would permit more optimisation (currently, on PowerPC 
and Alpha the code is very inefficient if a helper is called because the 
return address must be saved in a new generated stack frame).

Fabrice.

             reply	other threads:[~2003-06-08 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08 10:10 Fabrice Bellard [this message]
2003-06-08 10:20 ` [Qemu-devel] Sparc port David S. Miller
2003-06-08 10:52   ` Fabrice Bellard
2003-06-08 11:19     ` David S. Miller
2003-06-08 16:21       ` Fabrice Bellard
2003-06-09  5:28         ` David S. Miller
2003-06-08 11:23     ` Falk Hueffner

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=3EE30B8E.5070600@free.fr \
    --to=fabrice.bellard@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.