[kaffe] Re: DArwin6 JIT3
mvfranz at gmail.com
Mon Feb 21 07:08:52 PST 2005
Here is the details from Apple's Release notes
* The -traditional-cpp option has changed. In Apple GCC 3.1 and
earlier Apple GCC compilers, -traditional-cpp was used to toggle
between the standard GNU GCC preprocessor and Apple's own
preprocessor, "cpp-precomp". The GNU GCC compiler interpreted
-traditional-cpp differently on all other platforms. Since cpp-precomp
has been removed for Apple's GCC 3.3 compiler, the standard GNU
meaning of -traditional-cpp has been restored. By default, the GCC 3.3
preprocessor conforms to the ISO C standard. Using the -tradtional-cpp
option means the C preprocessor should instead try to emulate the old
So, Apple's compilers use these flags:
GCC 2.95 uses -traditional-cpp - Apple non-standard interpretation
GCC 3.1 uses -no-cpp-precomp
GCC 3.3 restored to the standard GCC flag usage
Hope that clears things up. ;)
On Mon, 21 Feb 2005 11:44:17 +0100, Dalibor Topic <robilad at kaffe.org> wrote:
> Riccardo wrote:
> > In <421880E1.3010507 at kaffe.org> Dalibor Topic wrote:
> >>>This might not be necessary on darwin7 since I think Apple changed
> >>>the way the compiler works for gcc 3.3. I can post the release notes
> >>>link that describes the changes for darwin 7. It also provides some
> >>>background on the darwin 5 -> 6 -> 7 changes.
> >>I've made -no-cpp-precomp the default in general. Chances are others
> >>broke gcc in the same way Apple did by turning the half-baked feature
> >>on by default before it was ready :)
> > could you add a compiler option check ?
> > darwin 7 needs none, darwin 6 needs -no-cpp-precomp and darwin 6 -
> > traditional or something similar...
> I'm afraid I didn't fully understand that remark.
> Does that mean that -no-cpp-precomp breaks something on some other
> darwin version? Or do you want to say that some other option is
> necessary additionally for some other darwin version?
> dalibor topic
> kaffe mailing list
> kaffe at kaffe.org
More information about the kaffe