From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] support for Mac OS X default compiler
Date: Mon, 19 Dec 2005 23:35:35 +0100 [thread overview]
Message-ID: <43A735B7.6000707@bellard.org> (raw)
In-Reply-To: <4069F0DD-347D-4555-9DC4-76F4AF1C988F@stud.tu-ilmenau.de>
Does -fno-tree-ch works on PC ?
Fabrice.
Joachim Henke wrote:
> I know that you have already discussed this on the list, and that you don't
> want to actively support GCC 4. But (at least on Mac OS X) only a fix in
> the build configuration is necessary to do the magic: op.c must be compiled
> with -fno-tree-ch (as already mentioned on this mailing list).
>
> GCC 4.0 is the default compiler since Mac OS 10.4 (Tiger). Apple still
> ships GCC 3.3 20030304 with Xcode 2.2, but doesn't seem to update it
> anymore. As the thread
> http://lists.gnu.org/archive/html/qemu-devel/2005-12/msg00077.html
> turned out, this old compiler has some obvious bugs (further bugs have been
> reported on the web - even with code that is less complex than QEMU).
>
> So why not support GCC 4 out of the box? The patch below does this, and
> should not hurt anybody. Users are still required to pass
> --disable-gcc-check to the configure script - but if they do, GCC 4 will
> get it's right command line options.
>
> I tested this with GCC 4.0.1 from Xcode 2.2, and all six softmmu targets
> were build without errors. Maybe it works on Linux PPC too?
>
> Would be nice, if you could apply this patch. It makes testing and building
> with GCC 4 easier.
>
> Best regards
> Jo.
next prev parent reply other threads:[~2005-12-19 22:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 19:36 [Qemu-devel] [PATCH] support for Mac OS X default compiler Joachim Henke
2005-12-19 22:35 ` Fabrice Bellard [this message]
2005-12-20 4:51 ` Joshua Root
2005-12-20 9:19 ` Daniel Egger
2005-12-20 11:16 ` Johannes Schindelin
2005-12-21 16:07 ` Joachim Henke
2005-12-20 11:57 ` Gwenole Beauchesne
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=43A735B7.6000707@bellard.org \
--to=fabrice@bellard.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.