From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] yet another proposed solution for gcc 4.x
Date: Sun, 4 Jun 2006 11:02:28 -0500 [thread overview]
Message-ID: <20060604160228.GA26124@tapir.sajinet.com.pe> (raw)
In-Reply-To: <200606041246.07373.paul@codesourcery.com>
<SNIP>
> Why bother? As you say gcc4 has issues other than just op.c, so why not just
> compile everything with the old gcc?
using the new gcc for the parts that can compile with it, could lead to better
performance in some cases, as well to help clean up the code for conformance
to newer standards and overall maintainability, while making also clear that
there are at least 2 different uses for gcc.
1) to compile the code for qemu to generate working binaries
2) to generate the code to be used for opcode translation
this will free us to work in whatever technical solutions are needed to fix 2)
in our own schedule without the pressure from all the people that now feel
compelled to "port" qemu to a newer gcc, because it is now the default on
their corresponding distributions.
the long term solution for 2) will be to get the qemu hand written code
generator completed, but could also include having an in tree version of gcc
that can be used for that simple purpose (like a dependant library/tool) or a
reference to an external one as a dependency, and as an intermediate step.
Carlo
PS. eventhough it wasn't the cleanest build, gcc-4.1.1 when used to build
everything but op.c resulted in working binaries on my gentoo 2006.0 amd64
system.
next prev parent reply other threads:[~2006-06-04 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 8:59 [Qemu-devel] yet another proposed solution for gcc 4.x Carlo Marcelo Arenas Belon
2006-06-04 11:46 ` Paul Brook
2006-06-04 16:02 ` Carlo Marcelo Arenas Belon [this message]
2006-06-05 11:21 ` Christian MICHON
2006-06-05 13:43 ` Carlo Marcelo Arenas Belon
2006-06-05 13:49 ` Paul Brook
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=20060604160228.GA26124@tapir.sajinet.com.pe \
--to=carenas@sajinet.com.pe \
--cc=paul@codesourcery.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).