From: Paul Brook <paul@codesourcery.com>
To: Blue Swirl <blueswir1@hotmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-system-sparc question?
Date: Fri, 13 Oct 2006 23:31:28 +0100 [thread overview]
Message-ID: <200610132331.28882.paul@codesourcery.com> (raw)
In-Reply-To: <BAY104-F78187B88633A12B4AF4E0FF140@phx.gbl>
On Wednesday 11 October 2006 18:20, Blue Swirl wrote:
> >Sounds like you just want a bare-metal cross. There's absolutely no reason
> >to
> >run the editor, compiler or assembler on the target machine.
> >Many targets even have gdb simulators (MIPS, ARM and PPC do).
>
> I disagree, it's much easier to use a native compiler than to build a cross
> compiler, even with crosstool.
Well, with native toolchains you get prebuilt binaries from your system
vendor, so building them is a non-issue.
I don't believe that they're much easier to use in this context. If you're
building prepackaged worktation software you might hit problems with crappy
configure scripts. For a teaching environment I wouldn't expect it to be a
problem, especially given the alternative is probably running on embedded dev
boards.
> I don't think other compilers than GCC even support
> cross setups.
That's definitely not true. Certainly anything targeting embedded systems are
cross compilers (the target too small/slow to consider compiling natively),
and I'd guess the same is true for many HPC systems (You don't want the
clutter on your compute machines, esp. if they're used via batch jobs).
In my experience pretty much all development is done with cross compilers from
workstations or commodity compile farms. This means windows/x86-linux, or
maybe a few crufty old solaris boxes left over from when sparc was fast :-)
> BTW, we could easily design and implement an ideal CPU just for Qemu
> purposes. It could be unlike any existing hardware, for example with zero
> or thousands of registers. The problem would be making a compiler for the
> CPU, also porting some OS to it. Any GCC and Linux guru volunteers? CS
> research projects?
There's no such think as an Ideal cpu. It's like picking the right
religion :-) If you want a toy cpu, there are things like mmix.
While arm, ppc, mips, sparc, etc each have their own peculiarities, they're
all reasonably clean architectures.
Paul
next prev parent reply other threads:[~2006-10-13 22:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 16:40 [Qemu-devel] qemu-system-sparc question? Ishwar Rattan
2006-10-10 17:55 ` K. Richard Pixley
2006-10-10 18:59 ` WaxDragon
2006-10-10 19:10 ` Ishwar Rattan
2006-10-10 20:34 ` Blue Swirl
2006-10-10 20:44 ` Ishwar Rattan
2006-10-10 22:00 ` Marco Matthies
2006-10-11 2:39 ` Paul Brook
2006-10-11 12:05 ` Ishwar Rattan
2006-10-11 17:20 ` Blue Swirl
2006-10-11 17:32 ` K. Richard Pixley
2006-10-11 17:32 ` Marco Matthies
2006-10-11 18:04 ` Brian Wheeler
2006-10-11 19:28 ` Johannes Schindelin
2006-10-11 19:38 ` Blue Swirl
2006-10-11 20:02 ` K. Richard Pixley
2006-10-13 22:31 ` Paul Brook [this message]
2006-10-14 8:14 ` Blue Swirl
2006-10-14 14:11 ` Paul Brook
2006-10-10 23:51 ` Aurelien Jarno
-- strict thread matches above, loose matches on Subject: below --
2006-10-11 21:03 Ben Taylor
2006-10-11 22:38 ` Johannes Schindelin
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=200610132331.28882.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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).