Displaying 4 results from an estimated 4 matches for "codewarri".
Did you mean:
codewarr
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
...with llvm-gcc 4.2 with no major issues. On 10.5 with Xcode 3.1.4, it is a different story. Xcode 3.1.4 contains an old version of llvm-gcc 4.2 which can't build our applications. There are 2 causes of the compilation failure:
>
> - llvm-gcc 4.2 contained in Xcode 3.1.4 can't compile CodeWarrior or Microsoft inline assembly.
>
> - llvm-gcc 4.2 contained in Xcode 3.1.4 doesn't recognize some i386 inline assembly instructions ("mov edx,aFloat" where aFloat is a float*).
Right. llvm-gcc in 3.1.4 is really really ancient and buggy. I really don't recommend using i...
2010 Jul 24
5
[LLVMdev] gcc 4.2 to llvm-gcc 4.2 transition
...e projects with llvm-gcc 4.2 with no major issues. On 10.5 with Xcode 3.1.4, it is a different story. Xcode 3.1.4 contains an old version of llvm-gcc 4.2 which can't build our applications. There are 2 causes of the compilation failure:
- llvm-gcc 4.2 contained in Xcode 3.1.4 can't compile CodeWarrior or Microsoft inline assembly.
- llvm-gcc 4.2 contained in Xcode 3.1.4 doesn't recognize some i386 inline assembly instructions ("mov edx,aFloat" where aFloat is a float*).
These issues prevent us to switch from gcc 4.2 to llvm-gcc 4.2. We could switch our build system to 10.6 but...