similar to: [LLVMdev] Major i386 optimization bug in Clang++?

On 10.10.2011, at 16:10, Alexandre Colucci wrote: > 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

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

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

The problem is in your code, not the compiler. You're casting an unaligned char* to an int*, even though an int* pointer must be 4-byte aligned in every ARM ABI that I've ever seen. On Jan 23, 2012, at 6:14 AM, Alexandre Colucci wrote: > Hi, > > I think I discovered a major armv7 optimization bug in Clang. I create a simple test case which exhibits the issue. > When you

On Thu, Jun 23, 2016 at 7:36 PM, Tim Northover <t.p.northover at gmail.com> wrote: > On 23 June 2016 at 06:31, vivek pandya via cfe-dev > <cfe-dev at lists.llvm.org> wrote: > > I am running OS X, when I build clang++ from source and use it to compile > > .cpp files it fails as it is not able to find C++ header. I am not > building > > libc++ along with llvm

Hello, I am running OS X, when I build clang++ from source and use it to compile .cpp files it fails as it is not able to find C++ header. I am not building libc++ along with llvm and clang. using -stdlib=libstdc++ solves problem partially but it fails when using C++11 threads, again it can't find <thread>, to get this work clang++ should work with -stdlib=libc++ but it fails with

Hi Vivek, you can also include these lines below to your ~/.bash_profile: LLVM_BUILD="/Developer/llvm/build" # Path to your build directory alias new-clang="$LLVM_BUILD/bin/clang -Wno-expansion-to-defined -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include" alias new-clang++="$LLVM_BUILD/bin/clang++

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

Hi, the subject says it all... After some experimenting, I got a bit confused as far as what the proper thing to do might be.... I build llvm/clang from trunk sources on OSX Lion 10.7.3 (i.e. x86_64-apple-darwin11.3.0 to speak GNU's platform-ese) where I also have successfully built a fsf-gcc 4.6.2 (and lately a 4.7 for that matter) from sources. Now, I think I understand that by playing

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

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

On Wed, Jul 6, 2016 at 1:21 PM, Mehdi Amini via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > On Jun 23, 2016, at 11:15 AM, Cristianno Martins via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > Hi Vivek, > > you can also include these lines below to your ~/.bash_profile: > > LLVM_BUILD="/Developer/llvm/build" # Path to your build directory

Hello LLVM/Clang developers, We recently switched to use the same clang version on all our platforms. This included switching from apple-clang from xcode to a pre-built binary we downloaded from llvm.org. We noticed that this actually came with a pretty big performance regression in compile times. If we do the simplest test program like this: #include <string> #include <iostream>

Hi, Currently, I can build lld/llvm on Fedora 17 but fail to build it on iMac. The commands I use as follows. Anyone can help me? Or is there the lld mail list I can post the question? Linux/Fedora can be built by the following command cmake -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_FLAGS=-std=c++11 -DCMAKE_BUILD_TYPE=Debug -G "Unix Makefiles" ../src/ make iMac

On Jun 12, 2014, at 4:37 PM, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > > > On 6/12/14, 3:07 PM, Joseph wrote: >> Hi Dan, >> >> >> So now that the includes are being found building the tutorial results in 74 warnings and 20 errors. Heres a couple examples: >> >> In file included from

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

On 12/26/12 12:32 AM, Rick Mann wrote: > I'm trying to make a library in Xcode that links against LLVM. I used the STL C++ template in Xcode 4.5.2, added libLLVMCore.a and libLLVMSupport.a to the link binaries phase, and made this call in my code: > > llvm::LLVMContext& llvmCTX = llvm::getGlobalContext(); > > I get link errors against std::string and other STL classes: >

I'm trying to make a library in Xcode that links against LLVM. I used the STL C++ template in Xcode 4.5.2, added libLLVMCore.a and libLLVMSupport.a to the link binaries phase, and made this call in my code: llvm::LLVMContext& llvmCTX = llvm::getGlobalContext(); I get link errors against std::string and other STL classes: Undefined symbols for architecture x86_64:

I don’t think Apple disable assertion on the release build. I remember having clang and llvm crash because of assertion failure regularly at some point in the past. Nowadays, it is far more unusual to get a clang crash, so I can’t tell, but I doubt they change the configuration. > Le 20 nov. 2018 à 16:32, Jack Howarth via cfe-dev <cfe-dev at lists.llvm.org> a écrit : > > The

Le 8 août 2013 à 07:22, gamma_chen <gamma_chen at yahoo.com.tw> a écrit : > Hi, > > Currently, I can build lld/llvm on Fedora 17 but fail to build it on iMac. The commands I use as follows. Anyone can help me? Or is there the lld mail list I can post the question? > > Linux/Fedora can be built by the following command > cmake -DCMAKE_CXX_COMPILER=clang++