From: "Mulyadi Santosa" <mulyadi.santosa@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] WE NEED GCC 4 please
Date: Mon, 21 Jan 2008 10:39:08 +0700 [thread overview]
Message-ID: <f284c33d0801201939q70a5279dqcc79fc707adedbb1@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0801202339010.5731@racer.site>
Hi...
If I may jump into the pool...
> I plan to work around the MinGW issue by guarding the offending part by
> "#ifdef GCC...", even if I have been told that it works only by chance
> (but it works, whereas any other option I tried does not).
Ehm, should we better wait a bit for fabrice to complete his code code
generator? then we can be freed (totally?) from gcc version
dependency? it's not that I ignore people's effort to make qemu gcc4
compatible...but I just think it will save us from more work in the
future (making it always gcc 3 compatible) and thus progress to more
demanding area like truly support SVM/VT, better SMP and so on.
just 2 cents opinion...
regards,
Mulyadi.
next prev parent reply other threads:[~2008-01-21 3:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 19:31 Re : [Qemu-devel] WE NEED GCC 4 please Sylvain Petreolle
2008-01-20 20:11 ` Mike Frysinger
2008-01-20 21:14 ` Johannes Schindelin
2008-01-20 22:26 ` Mike Frysinger
2008-01-20 22:38 ` Sunil Amitkumar Janki
2008-01-20 22:56 ` Mike Frysinger
2008-01-20 23:04 ` Philip Boulain
2008-01-20 22:59 ` Andreas Färber
2008-01-20 23:40 ` Johannes Schindelin
2008-01-21 3:39 ` Mulyadi Santosa [this message]
2008-01-21 7:19 ` Alexander Graf
2008-01-21 11:18 ` Johannes Schindelin
2008-01-21 11:30 ` Mulyadi Santosa
2008-01-21 12:45 ` Andreas Färber
2008-01-21 13:02 ` Johannes Schindelin
2008-01-21 13:51 ` Julian Seward
2008-01-21 14:58 ` Ronan Keryell
2008-01-21 15:36 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2008-01-20 2:34 renatogallo
2008-01-20 18:40 ` Jérôme PRIOR
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=f284c33d0801201939q70a5279dqcc79fc707adedbb1@mail.gmail.com \
--to=mulyadi.santosa@gmail.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).