search for: llvmsvn

Hi All, I built the binaries from the 3.1 final tag (http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_31/final/ etc) as below: > ../llvm/configure --enable-targets=host-only --prefix=/local/mnt/workspace/ashoknn/crd/neo/llvmsvn/build/bin > make install I notice that I can compile a program using clang as below: > ashoknn at ashoknn-vm:/local/mnt/workspace/ashoknn/crd/neo/temp/jit$clang test.c > ashoknn at ashoknn-vm:/local/mnt/workspace/ashoknn/crd/neo/temp/jit$ If I try to generate the bitcode only, it gi...

...47 PM, Ashok Nalkund wrote: >> Hi All, >> I built the binaries from the 3.1 final tag >> (http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_31/final/ etc) as below: >> >>> ../llvm/configure --enable-targets=host-only --prefix=/local/mnt/workspace/ashoknn/crd/neo/llvmsvn/build/bin >>> make install >> >> I notice that I can compile a program using clang as below: >> >>> ashoknn at ashoknn-vm:/local/mnt/workspace/ashoknn/crd/neo/temp/jit$clang test.c >>> ashoknn at ashoknn-vm:/local/mnt/workspace/ashoknn/crd/neo/temp/j...

...lp? On 5/16/2012 2:47 PM, Ashok Nalkund wrote: > Hi All, > I built the binaries from the 3.1 final tag > (http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_31/final/ etc) as below: > >> ../llvm/configure --enable-targets=host-only --prefix=/local/mnt/workspace/ashoknn/crd/neo/llvmsvn/build/bin >> make install > > I notice that I can compile a program using clang as below: > >> ashoknn at ashoknn-vm:/local/mnt/workspace/ashoknn/crd/neo/temp/jit$clang test.c >> ashoknn at ashoknn-vm:/local/mnt/workspace/ashoknn/crd/neo/temp/jit$ > > If I try...

...wrote: >>> Hi All, >>> I built the binaries from the 3.1 final tag >>> (http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_31/final/ etc) as below: >>> >>>> ../llvm/configure --enable-targets=host-only --prefix=/local/mnt/workspace/ashoknn/crd/neo/llvmsvn/build/bin >>>> make install >>> >>> I notice that I can compile a program using clang as below: >>> >>>> ashoknn at ashoknn-vm:/local/mnt/workspace/ashoknn/crd/neo/temp/jit$clang test.c >>>> ashoknn at ashoknn-vm:/local/mnt/workspace...

...nline asm not supported by this streamer because we don't have an asm parser for this target > > I add back the call to InitializeNativeTargetAsmParser() in lli.cpp, but compilation fails: Makes sense. >> make[4]: Leaving directory `/local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/tools/clang/tools/arcmt-test' >> /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/tools/lli/Debug+Asserts/lli.o: In function `llvm::InitializeNativeTargetAsmParser()': >> /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/include/llvm/Support/TargetS...

...inline assembly), not the MCJIT. >>>>> >>>> >>>> Do I need to enable anything at configure, my configure looks like this: >>>>> ../llvm/configure --enable-libffi --enable-targets=host-only --prefix=/local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/bin >>>> >>>> I added the enable-libffi when trying to figure out resolving external libs. >>>> >>> >>> >>> No, selecting MCJIT vs. the old JIT is done in the EngineBuilder. If you're using lli, you can pass -use-mcjit on the...

...e error: > LLVM ERROR: Inline asm not supported by this streamer because we don't have an asm parser for this target I add back the call to InitializeNativeTargetAsmParser() in lli.cpp, but compilation fails: > make[4]: Leaving directory `/local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/tools/clang/tools/arcmt-test' > /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/tools/lli/Debug+Asserts/lli.o: In function `llvm::InitializeNativeTargetAsmParser()': > /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/include/llvm/Support/TargetSelect.h:...

...ing the trunk of svn. I'm trying to get inline-asm working on X86. So I added call to: > InitializeNativeTargetAsmParser() during initialization. However, this causes a linking error: > llvm[2]: Linking Debug+Asserts executable lli > /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/tools/lli/Debug+Asserts/lli.o: In function `llvm::InitializeNativeTargetAsmParser()': > /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/include/llvm/Support/TargetSelect.h:149: undefined reference to `LLVMInitializeX86AsmParser' > collect2: ld returned 1 exit status...

...e, you're running the old JIT (which does indeed not support inline assembly), not the MCJIT. > Do I need to enable anything at configure, my configure looks like this: > ../llvm/configure --enable-libffi --enable-targets=host-only --prefix=/local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/bin I added the enable-libffi when trying to figure out resolving external libs. thanks, ashok

...(which does indeed not support inline assembly), not the MCJIT. >>> >> >> Do I need to enable anything at configure, my configure looks like this: >>> ../llvm/configure --enable-libffi --enable-targets=host-only --prefix=/local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/bin >> >> I added the enable-libffi when trying to figure out resolving external libs. >> > > > No, selecting MCJIT vs. the old JIT is done in the EngineBuilder. If you're using lli, you can pass -use-mcjit on the command line. If you're using your own drive...

...tcode file that I'm trying to load/execute using lli as below but it reports an error about unresolved symbol: > LLVM ERROR: Program used external function '_ZNKSt3__16locale9use_facetERNS0_2idE' which could not be resolved! > lli: /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/lib/Support/ThreadLocal.cpp:54: virtual llvm::sys::ThreadLocalImpl::~ThreadLocalImpl(): Assertion `errorcode == I've tried loading the following libs when running lli: > lli \ > -load=libQtCore.so.4 \ > -load=libpthread.so.0 \ > -load=libm.so.6 \ > -load=libgcc_s.so.1 \...

...ng the old JIT (which does indeed not support inline assembly), not the MCJIT. >> > > Do I need to enable anything at configure, my configure looks like this: >> ../llvm/configure --enable-libffi --enable-targets=host-only --prefix=/local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/bin > > I added the enable-libffi when trying to figure out resolving external libs. > No, selecting MCJIT vs. the old JIT is done in the EngineBuilder. If you're using lli, you can pass -use-mcjit on the command line. If you're using your own driver, you can use the lli....

...d not support inline assembly), not the MCJIT. >>>> >>> >>> Do I need to enable anything at configure, my configure looks like this: >>>> ../llvm/configure --enable-libffi --enable-targets=host-only --prefix=/local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/bin >>> >>> I added the enable-libffi when trying to figure out resolving external libs. >>> >> >> >> No, selecting MCJIT vs. the old JIT is done in the EngineBuilder. If you're using lli, you can pass -use-mcjit on the command line. If you...

The options is cmake -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_INSTALL_PREFIX=~software/llvmsvn -DCMAKE_EXPORT_COMPILE_COMMANDS=ON /home/xxx/lsoftware/llvm-3.2-svn $make $make install On Fri, Jun 28, 2013 at 12:37 PM, Eric Christopher <echristo at gmail.com>wrote: > On Thu, Jun 27, 2013 at 6:04 PM, Eric Lu <eirc.lew at gmail.com> wrote: > > Hi, Ben > > gcc versi...

...I'm > trying to load/execute using lli as below but it reports an error about > unresolved symbol: >> LLVM ERROR: Program used external function '_ZNKSt3__16locale9use_facetERNS0_2idE' which could not be resolved! >> lli: /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/lib/Support/ThreadLocal.cpp:54: virtual llvm::sys::ThreadLocalImpl::~ThreadLocalImpl(): Assertion `errorcode == > > I've tried loading the following libs when running lli: >> lli \ >> -load=libQtCore.so.4 \ >> -load=libpthread.so.0 \ >> -load=libm.so.6 \ &...

On Sat, Jun 29, 2013 at 8:41 AM, Eric Lu <eirc.lew at gmail.com> wrote: > The options is > cmake -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_INSTALL_PREFIX=~software/llvmsvn > -DCMAKE_EXPORT_COMPILE_COMMANDS=ON /home/xxx/lsoftware/llvm-3.2-svn > > That would do it; Debug builds are roughly 2x slower than Release builds. -Eli -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments...

On Thu, Jun 27, 2013 at 6:04 PM, Eric Lu <eirc.lew at gmail.com> wrote: > Hi, Ben > gcc version is: 4.7.0 > clang version is: 3.2 > > The command options are: > 1) clang > generated object files: clang -O3 -c *.c -o x.o > link: clang *.o -lm -o mpeg2enc > > 2) gcc > generated object files: gcc -O3 -c *.c -o x.o > link: gcc *.o -lm -o mpeg2enc >

Hello, Could someone please tell me why LLVM and clang downloaded from here: svn co http://llvm.org/svn/llvm-project/llvm/trunk llvmsvn co http://llvm.org/svn/llvm-project/cfe/trunk clang and generated using cmake: cmake -G "Visual Studio 15 2017" ../llvm does not compile in Visual Studio? I am using Batch Build in Visual Studio and I have selected only ALL_BUILD project to build as required in step 7 from here. | |...

...trying to load/execute using lli as below but it reports an error about >> unresolved symbol: >>> LLVM ERROR: Program used external function '_ZNKSt3__16locale9use_facetERNS0_2idE' which could not be resolved! >>> lli: /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/lib/Support/ThreadLocal.cpp:54: virtual llvm::sys::ThreadLocalImpl::~ThreadLocalImpl(): Assertion `errorcode == >> >> I've tried loading the following libs when running lli: >>> lli \ >>> -load=libQtCore.so.4 \ >>> -load=libpthread.so.0 \ >&gt...

On May 14, 2012, at 9:07 AM, Ashok Nalkund <ashoknn at qualcomm.com> wrote: > I was able to get past the error by calling InitializeNativeTargetAsmParser() in my code. Now I have a failure in resolving external libraries, so looking into that (recompiled with --enable-ffi but I now get an error LLVMgold.so not found). > > Then I hda to disable the following code in