From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] yet another proposed solution for gcc 4.x
Date: Sun, 4 Jun 2006 12:46:06 +0100 [thread overview]
Message-ID: <200606041246.07373.paul@codesourcery.com> (raw)
In-Reply-To: <20060604085935.GB24853@tapir.sajinet.com.pe>
On Sunday 04 June 2006 09:59, Carlo Marcelo Arenas Belon wrote:
> Greetings,
>
> attached patch, adds a ./configure option for setting the C compiler that
> will be used to build op.c for each of the targets; letting the user
> compile everything else with gcc 4.x if configured as the default C
> compiler while isolating the opcode generation which currently relies in
> gcc 3.x for dyngen to be able to make sense of it.
Why bother? As you say gcc4 has issues other than just op.c, so why not just
compile everything with the old gcc?
Paul
next prev parent reply other threads:[~2006-06-04 11:46 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 [this message]
2006-06-04 16:02 ` Carlo Marcelo Arenas Belon
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=200606041246.07373.paul@codesourcery.com \
--to=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).