search for: timac

On Sat, 24 Jul 2010 13:41:42 +0200 Alexandre Colucci <timac at timac.org> wrote: > 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. Since you are switching compilers, why not switch to clang instead of llvm-gcc? Best regards, --Edwin

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

...contains gcc predefined macro and we also have some third party libraries. With llvm-gcc we would keep the gcc parser which means less compatibility issues. - I am not sure if clang can generate code that runs on 10.5. Alexandre > On Sat, 24 Jul 2010 13:41:42 +0200 > Alexandre Colucci <timac at timac.org> wrote: > >> 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. > > Since you are switching compilers, why not switch to clang instead of > llvm-gcc? >...

Hey, My projects are not compiling on 10.5 using llvm-gcc 4.2 in Xcode 3.1.4. These are caused by some llvm bugs that are now fixed. Since Apple will not release a Xcode update for 10.5, I am trying to compile a recent version of llvm-gcc 4.2 (from the LLVM 2.7 branch - but I could use ToT if this helps) to use on 10.5 intel. I easily built llvm-gcc-4.2 on 10.5 intel by following the README.LLVM

Hi, llvm-gcc 4.2 generates warnings when I compile inline assembly code that contains used labels with -Wunused-label. The generated code seems to work yet. gcc 4.2 doesn't generate those warnings. I haven't found any bugs regarding this issue in the llvm bug database. Does anyone know if this is a known llvm issue? Is it a warning that I can ignore and does not affect the generated

Hi, I think I discovered a major armv7 optimization bug in Clang. I create a simple test case which exhibits the issue. When you compile the attached file for armv7 with optimizations turned on (O2, O3 or Os), the binary generated led to a crash. The issue can't be reproduced when using GCC 4.2. It can't be reproduced with Clang when the optimization is turned off (O0). This issue can be

Hi, I am currently making the transition from gcc 4.2 to clang for the projects (mostly C++) I am working on. I think I discovered a major optimization bug in Clang++. I managed to create a simple (60 lines of code) test case which exhibits the issue. When you compile this file for i386 with optimizations turned on (O2, O3 or Os), you get an unexpected result. When you compile it for x86_64, or

In practice all Apple hardwares support misaligned accesses for single-register loads and stores. If a pointer is not aligned, LLVM should not use the double-register loads and stores. It should keep the two single-register loads instead of trying to optimize them as one unsupported double-register load. Note that this code compiled with GCC 4.2 runs perfectly whereas LLVM will produce a binary