From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lh5Ud-00058f-DL for qemu-devel@nongnu.org; Tue, 10 Mar 2009 13:11:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lh5Ub-00055I-Qo for qemu-devel@nongnu.org; Tue, 10 Mar 2009 13:11:50 -0400 Received: from [199.232.76.173] (port=35613 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lh5Ub-00054w-Cl for qemu-devel@nongnu.org; Tue, 10 Mar 2009 13:11:49 -0400 Received: from mail-bw0-f171.google.com ([209.85.218.171]:40722) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lh5Ua-00051o-RF for qemu-devel@nongnu.org; Tue, 10 Mar 2009 13:11:49 -0400 Received: by bwz19 with SMTP id 19so1525505bwz.34 for ; Tue, 10 Mar 2009 10:11:45 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 10 Mar 2009 19:11:44 +0200 Message-ID: Subject: Re: [Qemu-devel] Any update on SPARC/Solaris host? From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 3/10/09, Jonathan Kalbfeld wrote: > Hi All, > > I know I pester about this a lot, but I was curious if there were any > new developments on SPARC/Solaris host? > > Last version I can run on Solaris 10/SPARC is the January 13, 2008 > build, and I just wanted to find out if the sparc efforts had been > shelved. I'm about to build more recent 0.9.1 builds but I get a core > dump on my V210 when trying to boot the i386 emulator. There are still problems with the i386, Sparc is picky about alignment and the code generator does not handle the unaligned access case. The speed may not be very great if all accesses have to construct the words using byte accesses and shifts. But doesn't Sparc32 system emulator work? It does here at least on Linux and OpenBSD. > I can donate some hosting resources to development of the sparc > version, but I'm not much of a serious coder. I'm much more adept at > packaging it up and making it available as a finished product... Testing and reporting bugs is also very helpful. To give more information about crashes, just run the binary under GDB and when the crash happens, enter a "bt" (backtrace) command to GDB prompt.