qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Bochnig, Martin" <mb1x@gmx.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU on SPARC host - Summary and suggested vl.c PATCH
Date: Wed, 01 Sep 2004 16:33:06 +0200	[thread overview]
Message-ID: <4135DDA2.9040608@gmx.com> (raw)
In-Reply-To: <20040901111740.GA2112@linux-m68k.org>

Hi,

thank you for your valuable hints, thoughts, comments.

I hope I will manage to get things running - earlier or later.
Most of my systems are SPARC based (all except 1 PC).
Furthermore I would love to see people using QEMU on top of SPARC hw 
(both on Solaris and LinUX as well as *BSD).

I'll keep in touch with you / the ml.


Thanx,

Martin




Richard Zidlicky wrote:
> On Wed, Sep 01, 2004 at 04:57:51AM +0200, Bochnig, Martin wrote:
> 
>>(now in its own thread)
>>
>>Hi,
> 
> 
>>Now we SPARC-host users are on the horns of a dilemma: QEMU's existing 
>>SPARC support is optimized for SPARCv7 only.
>>While we are required to build for v9 / SPARC64, the build process gives 
>>tons of errors caused by invalid type definitions/invalid size castings 
>>and doesn't complete.
>>The whole sources may need to be adjusted (by a real hacker, not me).
>>I edited Makefile.target, Makefile and configure and tested several 
>>'-mcpu=' and '-m32' vs. '-m64' settings - including '-mcpu=ultrasparc 
>>-m32' which is to produce so called sparcv8plus ELF 32 binaries.
>>I tried to build statically.
>>I enabled bigendian and gprof in 'configure'.
>>The build did NEVER complete with '-mcpu=ultrasparc' - no matter how all 
>>the other variations looked like.
>>So I could never test or even tune my theoretical %tick code (BTW: The 
>>vl.o object builds fine).
>>op.o seemed to be broken and dyngen complained and was unable to 
>>generate op.h. :-((
>>
>>../dyngen -o op.h op.o
>>dyngen: ret; restore; not found at end of op_setbe_T0_subl
> 
> 
> so look at the code generated for op_setbe_T0_subl in op.o,
> eg objdump -S op.o. 
> Chances are that you have forgotten some no-reorder-block or 
> noomit-fp compiler flags. Or the instructions have been
> reordered in some new way by the compiler or some V9 specific
> opcode. Just figure out what the compiler does instead of
> "ret; restore" and strip off these instructions.
> 
> Richard
> 
> 

      reply	other threads:[~2004-09-01 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01  2:57 [Qemu-devel] QEMU on SPARC host - Summary and suggested vl.c PATCH Bochnig, Martin
2004-09-01  5:45 ` Gwenole Beauchesne
2004-09-01  7:38   ` Bochnig, Martin
2004-09-01 11:17 ` Richard Zidlicky
2004-09-01 14:33   ` Bochnig, Martin [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=4135DDA2.9040608@gmx.com \
    --to=mb1x@gmx.com \
    --cc=bochnig@pool.math.tu-berlin.de \
    --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).