qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu working openbsd/sparc64 yet?
Date: Sat, 4 Apr 2009 10:48:26 +0300	[thread overview]
Message-ID: <f43fc5580904040048s1c743640mf5b1b897f5d6db09@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580904011142v2611575bl9bf066059f7960a@mail.gmail.com>

On 4/1/09, Blue Swirl <blauwirbel@gmail.com> wrote:
> On 4/1/09, Vivek Ayer <vivek.ayer@gmail.com> wrote:
>  > what were your configure options? I'm getting an error using gmake at
>  >  i386-softmmu. I'm checking out the svn code to see if that's better.
>  >  If you can send me the build that you got working that'd be great. I
>  >  just need Linux on OpenBSD/sparc64 so I can go ahead and use MATLAB
>  >  and Mathematica.
>
>
> I guess those are x86 versions. The i386 emulator does not work on
>  Sparc because unaligned accesses are not handled yet by the code
>  generator. But it should build all right.

The problem wasn't unaligned accesses after all, but again env (%g5)
gets corrupted somewhere. With r6971 I get to the CD boot phase of
BIOS.

      parent reply	other threads:[~2009-04-04  7:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29  4:43 [Qemu-devel] qemu working openbsd/sparc64 yet? Vivek Ayer
2009-03-29  9:12 ` Blue Swirl
2009-04-01  5:04   ` Vivek Ayer
2009-04-01 18:42     ` Blue Swirl
2009-04-01 19:58       ` Vivek Ayer
2009-04-01 21:29         ` Vivek Ayer
2009-04-01 22:17           ` Vivek Ayer
2009-04-03  4:40             ` Vivek Ayer
2009-04-03 16:58               ` Blue Swirl
2009-04-03 19:49                 ` Vivek Ayer
2009-04-03 21:02                   ` Vivek Ayer
2009-04-04  5:49                     ` Blue Swirl
2009-04-03 16:50         ` Blue Swirl
2009-04-04  7:48       ` Blue Swirl [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=f43fc5580904040048s1c743640mf5b1b897f5d6db09@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --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).