similar to: [LLVMdev] Using LLVM components

Hi All, The following crashes in CreateGlobalStringPtr: #include "llvm/Support/DataTypes.h" #include "llvm/LLVMContext.h" #include "llvm/Module.h" #include "llvm/Constants.h" #include "llvm/Function.h" #include "llvm/BasicBlock.h" #include "llvm/ExecutionEngine/ExecutionEngine.h" #include

I am getting this error on FreeBSD-8.1 (amd64): llvm[1]: Linking Debug+Asserts Shared Library libLLVM-2.8svn.so /tmp/llvm-svn/llvm-objects/Debug+Asserts/lib/libLLVMSystem.a(Program.o)(.text+0xa2b): In function `llvm::sys::Program::Execute(llvm::sys::Path const&, char const**, char const**, llvm::sys::Path const**, unsigned int, std::basic_string<char, std::char_traits<char>,

Jeffrey Yasskin wrote: >> Would you try the patch at >> http://codereview.appspot.com/download/issue968046_1.diff? It should >> make the BSDs fall into the same path as Linux, and since you use gnu >> ld, that should work for you. >> > > Ping? > Sorry for the delay. Here is what I am getting after applying the patch: gmake[2]: Leaving directory

On Tue, May 4, 2010 at 5:31 PM, Yuri <yuri at tsoft.com> wrote: > Jeffrey Yasskin wrote: >>> >>> Would you try the patch at >>> http://codereview.appspot.com/download/issue968046_1.diff? It should >>> make the BSDs fall into the same path as Linux, and since you use gnu >>> ld, that should work for you. >>> >> >> Ping?

Thanks very much for all of your answer. I was confused by definition of 'portable' by my own thinking. Now I Correct that. (ILP32 is in another project, It's my typo. Thanks) So let me make a conclusion about this. LLVM IR can be a portable language, just depending on our front-end configuration or origin language limits. Did I mistake that? Thank a lot all of you. 2010/12/22

Dear all, I cannot find the answer of this question. We all know LLVM IR is portable, but it uses ILP32 and record the target layout within the IR. target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64 :64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" target triple = "x86_64-linux-gnu" It seems it already assigned

Dear r-helpers, Here I would like to have your kind helps on generating Venn diagram. There are some packages within R on this task, like venneuler, VennDiagram, vennerable. But, vennerable can not be installed on my Mac book. It seems VennDiagram can not work on my data. And, venneuler may have generated a wrong Venn diagram to me. Do you have any experience/expertise on those Venn diagram?

Dear all, I heard a different way to solve it. $ apt-get install libc6-dev-amd64 Maybe this can help? 2010/12/30 Anton Korobeynikov <anton at korobeynikov.info> > Hello > > > Thanks for the tip. My PS3 workstationn is installed a 32-bit OS. I will > Please carefully read the readme.llvm file in the llvm-gcc source > directory. > At least it will give some hints how

Hi all, in this case: ... int* p = ... int* q = p; ... How can I know that data-flow from p to q, i.e., which LLVM pass of header files could I use? Thank you all. -- Best regards, Wen-Han -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110430/a9164c60/attachment.html>

OK. Thank you. What I want to do is: Fix source code in-place, then feed it to compiler normally. I assume I can fix source code in-place using clang::SourceManager, but I cannot find the appropriate API. Now I know that way is infeasible. Thanks again. 2011/5/5 Joshua Warner <joshuawarner32 at gmail.com> > Wen-Han, > > It sounds like there are two problems here: first is

I'm adding OProfile support to the JIT (patch at http://codereview.appspot.com/89041), and I'm running into trouble with getting llvm-config to print the right things to let external programs link. For some background, oprofile installs an agent library into <prefix>/lib/oprofile/libopagent.{a,so}. This isn't on the loader's default search path, even if <prefix>==/usr,