[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GCC and Clang
From: |
Po Lu |
Subject: |
Re: GCC and Clang |
Date: |
Fri, 11 Feb 2022 10:53:07 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux) |
Gregory Casamento <greg.casamento@gmail.com> writes:
> The way I see it, we have two ways we can go. In each, I have outlined
> what I believe needs to be done. It may or may not be complete:
>
> LLVM/Clang:
> 1) Improve libobjc2 such that it can
> a) function properly on a wider set of platforms. This means
> i) Correct build issues it has in on some environments.
> ii) Simplifying the build of it on Windows
> (i.e., don't require Visual Studio :))
Before dropping GCC support in GNUstep, could you please consult with
the developers of other GNU software which uses GNUstep?
I put quite some effort into getting the GNUstep port of Emacs into a
presentable state, which I would not have done had it not supported GCC.
There are also many machines that aren't supported by LLVM, which a
Clang-only GNUstep would not be able to run on.
> GCC
> 1) Implement syntactic sugar
> a) This includes @[], @{}, and @autorelease as well as
> b) Various @property directives
> c) Improvements to the GCC libobjc to support the new syntax
> i) Implementation of ARC in the runtime
It would be best for someone to work on it, but if nobody does, I think
GNUstep still needs to support GCC, at least for the important libraries
such as gnustep-gui and gnustep-base.
Thanks.
- GCC and Clang, Gregory Casamento, 2022/02/08
- Re: GCC and Clang,
Po Lu <=
- Re: GCC and Clang, Richard Frith-Macdonald, 2022/02/11
- Re: GCC and Clang, Riccardo Mottola, 2022/02/13
- Re: GCC and Clang, Gregory Casamento, 2022/02/13
- Re: GCC and Clang, Max Chan, 2022/02/14
- Re: GCC and Clang, t . heckert, 2022/02/25
- Re: GCC and Clang, Gregory Casamento, 2022/02/26
- Re: GCC and Clang, Max Chan, 2022/02/26
- Re: GCC and Clang, Gregory Casamento, 2022/02/28
Re: GCC and Clang, H. Nikolaus Schaller, 2022/02/11