From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org, blueswir1@hotmail.com
Subject: Re: [Qemu-devel] Sparc32/64 emulation test report
Date: Sun, 01 Apr 2007 22:11:43 +0200 [thread overview]
Message-ID: <461011FF.1020407@aurel32.net> (raw)
In-Reply-To: <BAY143-F350DF5B7920DBB6187B7AFF610@phx.gbl>
Blue Swirl a écrit :
> Sparc32 system emulator tests
>
For your information I recently tried to build gcc 4.1 in bootstrap mode
on both QEMU and real hardware (SparcStation 4) for C, C++, objc and
fortran. I than run the testsuite.
The testsuite gave identical results on both emulated and real hardware.
More impressive the binaries (including all .o files) in the build tree
were the same, minor strings containing hostname and date/time.
I used an SVN version of QEMU plus a few patches that have been applied
since then, except the std/stda in delay slot one.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
prev parent reply other threads:[~2007-04-01 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 19:21 [Qemu-devel] Sparc32/64 emulation test report Blue Swirl
2007-04-01 20:11 ` Aurelien Jarno [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=461011FF.1020407@aurel32.net \
--to=aurelien@aurel32.net \
--cc=blueswir1@hotmail.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).