Merging Apple's Objective-C 2.0 compiler changes

[Steven Bosscher]

On Tue, Sep 14, 2010 at 12:05 AM, Manuel López-Ibáñez
<lopezibanez@gmail.com> wrote:
>> I understand the benefit that existed before clang.  And my general
>> understanding is that clang C++ support is not yet complete, so there is
>> a benefit there, but only a temporary one.  I don't see a real benefit
>> going forward.
>
> Access to all the other GCC front-ends that the LLVM project has not
> (yet) reimplemented? Someone provided above a real user-case for
> gcc->llvm involving Fortran. I don't think dragon-egg development is
> stalled at all.

And some (including yours truly) consider this little more than theft.
Especially since there is GCC-bashing on the one side, and taking the
bits they like on the other.


>> Since for me benefits to users of gcc are pretty much the same as
>> benefits to gcc, yes, I see a benefit.
>
> By that rule, it is clearly beneficial for some gcc users to compile
> Fortran using dragon-egg to take advantage of OpenCL. Ergo, dragon-egg
> is beneficial to GCC.

No it "is" not, you "think it is", i.e. opinion. Again, I don't share
that opinion at all, because this means there is less motivation for
developers to add OpenCL to GCC itself.

Anyway, we're waaaaaaaaaaay off-topic here from the original question
about improving ObjC in GCC.

Ciao!
Steven