search for: lllvm

...if it's working for you I guess you don't need to worry about it. Too bad for me/us, though.) >> > > Ah, I take it back: in a clean build Clang tries to link ~llvm/build/bin/Debug/Debug/clang-tblgen (doubly wrong!) and also fails to link because the link paths are > > -Lllvm/build/bin/Debug/Debug > -Lllvm/build/lib/Debug > -Lllvm/build/lib > > ...but Xcode still built into llvm/build/Debug/lib. Looks like everything is working now, except that clang-tblgen is still being built into ~llvm/build/bin/Debug/Debug/clang-tblgen. I'll see if I can figure out...

...= 5; GenericValue gg((void*)(&p)); arg.push_back(gg); EE->runFunction(f1,arg); cout<<p&lt;&lt;endl;&lt;/b> the output is 0 Does anyone know how to pass the argument ? Chia Lun -- View this message in context: http://llvm.1065342.n5.nabble.com/how-to-use-lllvm-interpreter-api-tp51345.html Sent from the LLVM - Dev mailing list archive at Nabble.com.

...to change for Xcode, so if it's working for you I guess you don't need to worry about it. Too bad for me/us, though.) > Ah, I take it back: in a clean build Clang tries to link ~llvm/build/bin/Debug/Debug/clang-tblgen (doubly wrong!) and also fails to link because the link paths are -Lllvm/build/bin/Debug/Debug -Lllvm/build/lib/Debug -Lllvm/build/lib ...but Xcode still built into llvm/build/Debug/lib. Jordan

Hi, Takumi. Your CMake changes seem to be working just fine with the standalone Xcode build. However, the build products are still being put in bin/Debug instead of Debug/bin. Was that supposed to change yet? Maybe Xcode needs different settings? (I think I looked into this once and it was non-trivial to change for Xcode, so if it's working for you I guess you don't need to worry about

...for you I guess you don't need to worry about it. Too bad for me/us, though.) >>> >> >> Ah, I take it back: in a clean build Clang tries to link ~llvm/build/bin/Debug/Debug/clang-tblgen (doubly wrong!) and also fails to link because the link paths are >> >> -Lllvm/build/bin/Debug/Debug >> -Lllvm/build/lib/Debug >> -Lllvm/build/lib >> >> ...but Xcode still built into llvm/build/Debug/lib. > > Looks like everything is working now, except that clang-tblgen is still being built into ~llvm/build/bin/Debug/Debug/clang-tblgen. I'...

Hi Tom, hi Michael, Thank you for your help. I understand the linking problem. What I do not understand is how to debug the difference between two versions of compilers. This what I do (briefly): clang++-4 foobar.cpp -lLLVM -l/opt/llvm-3.9/lib clang++-5 foobar.cpp -lLLVM -l/opt/llvm-3.9/lib The first command produces a working executable, while the other one does not. I'm trying to understand whether I had this problem all the time but clang-4 could not see it, or there is no problem but clang-5 does something w...

...Debug+Asserts/AnalysisWrappers.o /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/GraphPrinters.o /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/PrintSCC.o /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/opt.o \ > -lLLVM-2.9svn -lpthread -lmalloc -lm It seems like you're missing a whole bunch of libraries on the command line. This is what I have when I compile it: -lLLVMipo -lLLVMScalarOpts -lLLVMInstCombine -lLLVMInstrumentation -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLLVMTarget -lLLVMMC -lLLVMAsm...

On 31 May 2018 at 08:41, Alex Denisov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I understand the linking problem. What I do not understand is how to debug the difference between two versions of compilers. > This what I do (briefly): > > clang++-4 foobar.cpp -lLLVM -l/opt/llvm-3.9/lib > > clang++-5 foobar.cpp -lLLVM -l/opt/llvm-3.9/lib If you add -v then Clang will output each individual command it runs to do that compilation (I'd expect 2: one compile step and one link step). As Tom & Michael said, the link step is most likely to be wrong. Yo...

.../mem.Tpo -c -o mem.o mem.cpp mv -f .deps/mem.Tpo .deps/mem.Po /bin/bash ../libtool --tag=CXX --mode=link clang -I../test -I/usr/include/llvm-c-3.2 -I/usr/include/llvm-3.2 -O0 -g3 -Wall -O0 -Wall -g3 -export-dynamic -module -avoid-version -O0 -Wall -o mem mem.o -L/usr/local/lib/beauty -lz -ldl -lLLVM-3.2 -L/usr/lib/llvm-3.2/lib -lstdc++ libtool: link: clang -I../test -I/usr/include/llvm-c-3.2 -I/usr/include/llvm-3.2 -O0 -g3 -Wall -O0 -Wall -g3 -O0 -Wall -o mem mem.o -Wl,--export-dynamic -L/usr/local/lib/beauty -lz -ldl -lLLVM-3.2 -L/usr/lib/llvm-3.2/lib -lstdc++ mem.o:(.rodata+0x90): undefined...

...ction-selection-3.7 avx-instruction-selection-3.8 g++ -Wall -o create-execution-engine-3.4.o -c create-execution-engine.cpp `llvm-config-3.4 --cxxflags` -I. gcc -Wall -o avx-instruction-selection-3.4 avx-instruction-selection.c `llvm-config-3.4 --cflags --ldflags` -I. create-execution-engine-3.4.o -lLLVM-3.4 g++ -Wall -o create-execution-engine-3.5.o -c create-execution-engine.cpp `llvm-config-3.5 --cxxflags` -I. gcc -Wall -o avx-instruction-selection-3.5 avx-instruction-selection.c `llvm-config-3.5 --cflags --ldflags` -I. create-execution-engine-3.5.o -lLLVM-3.5 g++ -Wall -o create-execution-engin...

...PM, Devang Patel <dpatel at apple.com> wrote: > In your example, you do not need to update debug info for @global_var at the moment. We are not identifying tls in debug info yet. Does that mean I will not be able to debug applications which use tls through gdb if they are build with gcc-lllvm or clang. > On Oct 13, 2010, at 8:30 AM, shankha wrote: > >> I do not face any issues debugging my test case. But while debugging >> my application >> through gdb I cannot make sense of the call stack. I do not see the >> function names in >> the call stack (wit...

...he dynamic link library(dll) > about all of llvm library, such as libLLVMCore.dll, libLLVMSupport.dll, and > so on. How should I do? You may do, "/path/to/configure --enable-shared=yes", to build LLVM-2.8svn.dll. On your project, you have to specify to linker, "-L/path/to/dll -lLLVM-2.8svn" (maybe with -Wl,--enable-auto-import) We provide not individual DLLs but a "BIG" one. We don't provide import libraries. I think "DLL" feature is still experimental, and I need more feedback. When you met any troubles with DLL, ask here or file bugs! Have fun...

Hello, everyone! 请键入文字或网站地址，或者上传文档 <http://translate.google.cn/?tr=f&hl=zh-CN>。 取消 <http://translate.google.cn/?tr=t&hl=zh-CN> I'm a newbie about llvm. Now, our project need the dynamic link library(dll) about all of llvm library, such as libLLVMCore.dll, libLLVMSupport.dll, and so on. How should I do? Thanks, yuanzheng. -------------- next part -------------- An HTML

...about all of llvm library, such as libLLVMCore.dll, libLLVMSupport.dll, > and > > so on. How should I do? > > You may do, "/path/to/configure --enable-shared=yes", > to build LLVM-2.8svn.dll. > On your project, you have to specify to linker, > "-L/path/to/dll -lLLVM-2.8svn" > (maybe with -Wl,--enable-auto-import) > > We provide not individual DLLs but a "BIG" one. > We don't provide import libraries. > > I think "DLL" feature is still experimental, and I need more feedback. > When you met any troubles with DLL,...

Will LLLVM dot releases include fixes for Clang as well? -- Regards, Konstantin

Hi, For lllvm 3.7 and before BUILD_SHARED_LIBS=ON would produce versioned shared libs like libLLVMLTO.so (symlink) libLLVMLTO.so.3.7 (symlink) libLLVMLTO.so.3.7.0 (real file) now it just builds an unversioned libLLVMLTO.so file which I believe is a problem because when a program links to llvm it generates a ru...

...y 2018 at 08:41, Alex Denisov via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> I understand the linking problem. What I do not understand is how to debug the difference between two versions of compilers. >> This what I do (briefly): >> >> clang++-4 foobar.cpp -lLLVM -l/opt/llvm-3.9/lib >> >> clang++-5 foobar.cpp -lLLVM -l/opt/llvm-3.9/lib > > If you add -v then Clang will output each individual command it runs > to do that compilation (I'd expect 2: one compile step and one link > step). > > As Tom & Michael said, the l...

...> /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/Gr! > aphPrinters.o > /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/PrintSCC.o > /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/opt.o > \ > > -lLLVM-2.9svn -lpthread -lmalloc -lm > > It seems like you're missing a whole bunch of libraries on the command > line. This is what I have when I compile it: > > -lLLVMipo -lLLVMScalarOpts -lLLVMInstCombine -lLLVMInstrumentation > -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLL...

...s libLLVMCore.dll, libLLVMSupport.dll, >> > and >> > so on. How should I do? >> >> You may do, "/path/to/configure --enable-shared=yes", >> to build LLVM-2.8svn.dll. >> On your project, you have to specify to linker, >> "-L/path/to/dll -lLLVM-2.8svn" >> (maybe with -Wl,--enable-auto-import) >> >> We provide not individual DLLs but a "BIG" one. >> We don't provide import libraries. >> >> I think "DLL" feature is still experimental, and I need more feedback. >> When yo...

...replace their system's C++ standard library?) > > I believe there is some work being done on that already < http://lists.llvm.org/pipermail/lldb-dev/2018-January/013186.html>, but I'm not sure what's the current state of it. Also, in the default configuration, LLDB will use lllvm::itaniumDemangle for demangling (although there is a build option to use cxa_demangle). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180306/14f392aa/attachment.html>