qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/target-sparc exec.h op.c op_helper.c op_me...
Date: Sat, 22 Sep 2007 22:34:28 +0200	[thread overview]
Message-ID: <46F57C54.1010105@aurel32.net> (raw)
In-Reply-To: <E9DEC8FF-ABF5-46B6-BE7A-67A4EE8F62A4@web.de>

Andreas Färber a écrit :
> Am 22.09.2007 um 22:06 schrieb Aurelien Jarno:
> 
>> I really doubt it is an endianness problem as the current CVS works
>> perfectly on GNU/Linux powerpc. The code in op_helper.c adds  
>> support for
>> target little endian access (sparc is big endian), but it is anyway  
>> not
>> used in openbios. We have to debug the problem and find what is wrong
>> with OS X:
>>
>> - Which version of GCC are you using?
> 
> I have a gcc 4.0.1 installed but configure appears to choose gcc-3.3:
> 
> $ gcc-3.3 --version
> gcc-3.3 (GCC) 3.3 20030304 (Apple Computer, Inc. build 1819)
> Copyright (C) 2002 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There  
> is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR  
> PURPOSE.
> 
>> - Could you please try to run qemu with -nographic?
> 
> I already tried that, it makes no difference - it hangs after  
> "starting qemu...".
> 
>> - Also could you please try to run qemu with -d in_asm,op and send us
>> /tmp/qemu.log?
> 
> Of course, see attached. (CVS HEAD configured as before, with .../ 
> qemu-system-sparc -boot d -cdrom ...solaris10sparc.iso -nographic -d  
> in_asm,op)
> 

Thanks, that's helpful, it looks like the "lduba" instructions is not
working correctly in your case. Now I have to find why.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

  reply	other threads:[~2007-09-22 20:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 19:10 [Qemu-devel] qemu/target-sparc exec.h op.c op_helper.c op_me Blue Swirl
2007-09-21 19:32 ` Andreas Färber
2007-09-21 20:25   ` Blue Swirl
2007-09-21 20:41     ` Andreas Färber
2007-09-21 20:26   ` Aurelien Jarno
2007-09-21 21:07     ` Aurelien Jarno
2007-09-21 21:20       ` Andreas Färber
2007-09-22 11:49         ` Aurelien Jarno
2007-09-22 12:07           ` Blue Swirl
2007-09-22 13:11           ` Andreas Färber
2007-09-22 17:50             ` Aurelien Jarno
2007-09-22 19:27               ` Andreas Färber
2007-09-22 20:06                 ` Aurelien Jarno
2007-09-22 20:23                   ` Andreas Färber
2007-09-22 20:34                     ` Aurelien Jarno [this message]
2007-09-22 21:21                       ` Andreas Färber
2007-09-22 21:41                       ` Aurelien Jarno
2007-09-22 21:58                         ` Andreas Färber
2007-09-22 23:11                           ` Aurelien Jarno
2007-09-23  8:44                             ` Andreas Färber
2007-09-25 17:45                             ` Andreas Färber
2007-09-26 11:05                               ` Aurelien Jarno
2007-09-28 14:37                                 ` Andreas Färber
  -- strict thread matches above, loose matches on Subject: below --
2008-02-24 14:10 Blue Swirl

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=46F57C54.1010105@aurel32.net \
    --to=aurelien@aurel32.net \
    --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).