similar to: [LLVMdev] Any understandable link error available for LLVM Clang?

Hey All; Meet the following link error using LLVM 2.0 based on XCode 4.0.1, I don't know what does it mean and how to fix it? please help, thanks. ld: bad codegen, pointer diff in ___cxx_global_var_init79 to global weak symbol __ZN5boost16exception_detail23exception_ptr_bad_allocILi42EE1eE for architecture armv7 clang: error: linker command failed with exit code 1 (use -v to see

Hi, I am facing problem when using CELT for iPad. I wonder if someone have experience with that, or someone have idea why it happened. I was able to compile libCelt (and lib Ogg) for iPad (iOS 4.2) and for iPad Simulator I added those libraries to my application, and it was successfully compiled and linked, but once the application start it immediately crash (even if I am not using any of the

It looks like it: [/Volumes/Files/yuchen_wu/dev/llvm/build]$ xcrun --show-sdk-path --sdk iphonesimulator /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk ________________________________ > Date: Wed, 20 Nov 2013 08:03:21 +0400 > Subject: Re: [LLVMdev] Can't compile compiler-rt, asan error > From: glider at

Can you please reconfigure and attach the full log of 'make VERBOSE=1' ? On Nov 20, 2013 8:25 AM, "Yuchen Wu" <yuchenericwu at hotmail.com> wrote: > It looks like it: > > [/Volumes/Files/yuchen_wu/dev/llvm/build]$ xcrun --show-sdk-path --sdk > iphonesimulator > >

Also, which version of OSX you're running? On Nov 20, 2013 8:32 AM, "Alexander Potapenko" <glider at google.com> wrote: > Can you please reconfigure and attach the full log of 'make VERBOSE=1' ? > On Nov 20, 2013 8:25 AM, "Yuchen Wu" <yuchenericwu at hotmail.com> wrote: > >> It looks like it: >> >>

Hi all, I'm a LLVM newbie and am working on a LLVM 3.5 code base. The project ( https://github.com/zhguanw/lin-analyzer) makes use of clang and reads C code. I'm trying to make it read C++ code. When I compile a kernel written in C with clang++, I get the following difference in the IR for a function declaration: When compiled with clang: declare void @convolution3d(float*, float*) #1

Hi, Is there a way to see what the default argument llc takes from clang/clang++ ? I'm debugging my backend with a very simple c++ program. Running through *clang++ -target myTarget -S simple.cpp -o simple.s * (bug does no show up) gives me different results from *clang++ -target myTarget -S -emit-llvm -o simple.cpp -o simple.ll* *llc simple.ll -o simple.s *(bug shows up) Just trying to

Hi John, > We have a new release of Clang with SAFECode technology for detecting > memory safety errors. Memory safety checking (SAFECode for short) can be > turned on with a single command line switch to clang/clang++. The > SAFECode techniques do not change the behavior of the clang/clang++ > compilers in any way when the switch is turned off, so this can be used > as a

Hi, not sure if this is the right place, but I am experiencing a problem using clang++ (3.9.1) with Boost Filesystem. I have this simple program: ------------------------------------------------------------------------ #include <iostream> #include <boost/filesystem.hpp> using namespace boost::filesystem; int main(int argc, char* argv[]) { if (argc < 2) { std::cout

When I try to do clang++ main.cpp -emit-llvm without -S, clang says that he can’t: clang: error: -emit-llvm cannot be used when linking why can’t it emit the IR in a complete compilation process? Is there a particular technical reason or just to avoid confusing jobs? -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Mon, May 28, 2012 at 07:42:12PM +0200, Mikael Lyngvig wrote: > Does Clang/Clang++ not have its own set of standard headers? Isn't this a > serious issue if Clang/Clang++ is ever to outdo GCC/G++? Is there any work > in progress on this? It provides the compiler-centric headers. It doesn't replace the rest of the C runtime library. That wouldn't make much sense. Joerg

On Jul 12, 2010, at 3:00 AM, Yuri wrote: > On 07/12/2010 00:23, Duncan Sands wrote: >> IIRC, __cxa_end_catch may throw an exception because it runs the destructor >> for the exception object, which can execute arbitrary user code and thus may >> throw an exception. This is why it is sometimes correct to use invoke for it. >> However in the case of your example it seems

There is no single LLVM IR for the entire compilation process in such a command line - separate IR is created for each source file, an object file is created, then those (native, non-IR) object files are linked together. So it's somewhat a invalid concept. In your case, since there's only one file anyway, just add -c and you should be fine (your IR won't include the standard

Does Clang/Clang++ not have its own set of standard headers? Isn't this a serious issue if Clang/Clang++ is ever to outdo GCC/G++? Is there any work in progress on this? Ideally, Clang would ship as a ready-to-use installation image that included everything needed to use it as the possibly best C and C++ compiler on the market. Or, am I ahead of myself again? Cheers, Mikael -- Love Thy

-disable-O0-optnone has no effect with anything other than -O0. -O0 being passed to clang also causes all functions to be marked noinline. I don't know if there is a command line option to turn that off. I recommend passing "-O1 -Xclang -disable-llvm-passes" to clang. Passing -O0 very specifically means disable optimizations. ~Craig On Sat, Jan 6, 2018 at 12:25 PM, toddy wang

*System:* Debian Linux Sid/Unstable amd64 *LLVM/Clang:* Trunk *Scenario:* In the past couple of days I've been compiling against trunk I get two separate and spurious hang ups with CMake. *Note:* I build against more than just X86 follow along the progress of other platforms, though just building for X86 produces the same results below. *Assumption:* Configure cmake with prior built

Why are you using build directions from "flang" which is a fortran compiler and maintained by different people than the LLVM/clang community? But then compiling C/C++ code? Their bug database should be used for filing bugs against the fortran compiler not a C/C++ compiler issue. ~Craig On Sat, Jan 6, 2018 at 1:04 PM, toddy wang <wenwangtoddy at gmail.com> wrote: > Thanks a

@Zhaopei, thanks for the clarification. @Craig and @Michael, for clang 4.0.1, -Xclang -disable-O0-optnone gives the following error message. From which version -disable-O0-optnone gets supported? [twang15 at c89 temp]$ clang++ -O0 -Xclang -disable-O0-optnone -Xclang -disable-llvm-passes -c -emit-llvm -o a.bc LULESH.cc error: unknown argument: '-disable-O0-optnone' [twang15 at c89

Here are the results of me playing around with the new EXPERIMENTAL release v3.1 of clang for Windows using MinGW32: 0. You don't need to go through the nightmare of building clang v3.1 yourself - it is right there on the download page, albeit at the very bottom. 1. Install MinGW32 in the directory C:\MinGW and nowhere else. Otherwise you'll get all sorts of errors about missing

Hello, For the last couple of days I struggled to find a way to compile LLVM with Clang for ARM. Now, I tried many variations of the settings, linkers and compilers, but I was able only to build for i386 and x86_64. My machine is an i386 iMac. This is my first attempt to cross-compile something, so probably I'm doing something incredible stupid. First, I'm not sure which compiler should