Displaying 4 results from an estimated 4 matches for "codewarrier".
2010 Jul 24
0
[LLVMdev] gcc 4.2 to llvm-gcc 4.2 transition
...third party libraries. With llvm-gcc we would keep the gcc parser which means less compatibility issues.
Clang should be very compatible with GCC and its extensions, except that it is more pedantic about enforcing C++ language rules. One major feature not supported by clang yet is "microsoft/codewarrier style inline assembly". Since you are apparently using this, Clang sounds like a non-starter for you for now.
> - I am not sure if clang can generate code that runs on 10.5.
It can, but it does not support powerpc (llvm-gcc does).
-Chris
2010 Jul 24
2
[LLVMdev] gcc 4.2 to llvm-gcc 4.2 transition
There are several reasons why I am currently not considering the transition to Clang (although I would love to switch to it):
- Clang (LLVM compiler 2.x) is only integrated by default in Xcode 4 which has not been released yet. I guess it might be possible to use Clang in Xcode 3.2 and Xcode 3.1.
- Clang is a new compiler and the C++ support is really new and might contain bugs. Moreover Apple
2010 Jul 24
0
[LLVMdev] gcc 4.2 to llvm-gcc 4.2 transition
On Jul 24, 2010, at 4:41 AM, Alexandre Colucci wrote:
> I am currently studying the possibility to make the transition from gcc 4.2 to llvm-gcc 4.2 for the projects I am working on.
> These projects are huge projects, most of the source code is written in C++ but we have objc, c and assembly code. We are targeting MacOSX 10.5 and MacOSX 10.6.
Ok, great!
> Our build system is currently
2010 Jul 24
5
[LLVMdev] gcc 4.2 to llvm-gcc 4.2 transition
Hi,
I am currently studying the possibility to make the transition from gcc 4.2 to llvm-gcc 4.2 for the projects I am working on.
These projects are huge projects, most of the source code is written in C++ but we have objc, c and assembly code. We are targeting MacOSX 10.5 and MacOSX 10.6.
Our build system is currently running on MacOSX 10.5 and uses Xcode 3.1.4 with gcc 4.2. It is used to