All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: qemu-devel@nongnu.org, fabrice.bellard@free.fr
Subject: Re: [Qemu-devel] Sparc port
Date: Sun, 08 Jun 2003 03:20:40 -0700 (PDT)	[thread overview]
Message-ID: <20030608.032040.08328976.davem@redhat.com> (raw)
In-Reply-To: <3EE30B8E.5070600@free.fr>

   From: Fabrice Bellard <fabrice.bellard@free.fr>
   Date: Sun, 08 Jun 2003 12:10:22 +0200

   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.
   
-mflat doesn't work, gcc doesn't obey -fno-delayed-branch when
-mflat is specified and that basically makes it useless.

Also, this feature of GCC is scheduled for deprecation.

   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.

This might work.   

I think all things that generated code could call should marked as
ONLY being invoked from generated code, and furthermore have a very
fixed environment that we can rely upon.

It is the only clean way to deal with this sparc issue in the long
term.

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08 10:10 [Qemu-devel] Sparc port Fabrice Bellard
2003-06-08 10:20 ` David S. Miller [this message]
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=20030608.032040.08328976.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=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.