similar to: [LLVMdev] llvm and glibc

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] llvm and glibc"

2007 Mar 26
1
[LLVMdev] llvm installation failure
I am trying to make and install a version of llvm that I check out of cvs last night. When I configured LLVM, I set the prefix to a directory inside my home directory. However, when I did a make install I got the following errors: llvm[3]: Installing Debug Bytecode Archive /lib/libc.a /usr/bin/install: cannot create regular file `/lib/libc.a': Permission denied make[3]: ***
2006 Apr 25
1
[LLVMdev] bytecode to c conversion
Is there a conversion tool to convert llvm bytecode into c code? Regards, Ryan -- Ryan M. Lefever [217.333.7231] [http://www.ews.uiuc.edu/~lefever]
2006 May 01
2
[LLVMdev] printf decleration
I am writing a pass where I need to make a function deceleration for printf. Below is the code I'm trying to use. ----- bool MyPass::runOnModule(Module &m) { vector<const Type*> args; args.push_back(PointerType::get(Type::SByteTy)); Function* f = m.getOrInsertFunction("printf", FunctionType::get(Type::IntTy, args, true)); ----- When I insert a call
2006 May 01
0
[LLVMdev] printf decleration
Ok, I think I figured it out. I talked to someone, and we figured out that when I make a call to printf with a constant string, I need to make a global variable and use getElementPtr to reference it. The modified call for accessing the printf is: /* m is Module*, f is Function*, i is Instruction* */ Constant* constStr = ConstantArray::get("test\n"); GlobalVariable* gv =
2007 Feb 22
1
[LLVMdev] opt -verify
I think I misread the doxygen. verifyFunction & verifyModule return false if no errors are detected. However, my question now becomes why does the code produced by my transform pass verification, but it causes an assertion failure in the byte reader when it (the code produced by my transform) is passed to another invocation of opt? Ryan M. Lefever wrote: > I also tried iterating
2006 Apr 25
3
[LLVMdev] src to src conversion
I am trying to use LLVM as a source to source C compiler. I use llvm-gcc to convert file.c->file.bc. Then I use opt to run my own compiler passes to convert file.bc->file.opt.bc. Then I use llc to convert file.opt.bc->file.opt.c. Now, I want to use normal gcc to compile file.opt.c into an executable. However, I'm getting the following errors: test.opt.c:89: warning:
2006 May 11
1
[LLVMdev] using cfrontend-1.6 and llvm-1.7
Is it safe to use the LLVM cfrontend 1.6 with LLVM 1.7 or the latest LLVM from CVS? I am running OS X 10.3.9, which I believe corresponds to Darwin kernel version 7.9.0. When I tried to use the 1.7 cfrontend, I could not get LLVM 1.7 or the LLVM from CVS to compile. However, when I used the 1.6 cfrontend (which is additionally labeled Darwin 7.9.0), I was able to get them to compile.
2007 Apr 06
0
[LLVMdev] llc assertion failure
On Fri, 2007-04-06 at 14:27 -0500, Ryan M. Lefever wrote: > Is a PR a bug report on the bugzilla database? Yes, so named because of the URL translation. I.e. http://llvm.org/PR123 takes you to bugzilla bug 123. PR == Problem Report. > I am also running > bugpoint to see if that yields anything. Okay, good. That might turn up something useful. If you suspect its a bug, please file
2007 Apr 06
2
[LLVMdev] llc assertion failure
Is a PR a bug report on the bugzilla database? I am also running bugpoint to see if that yields anything. Reid Spencer wrote: > Hi Ryan, > > On Fri, 2007-04-06 at 13:34 -0500, Ryan M. Lefever wrote: > >>I am running the following llvm-ld command to produce native code: >> >>llvm-ld -native -o code.exe code.bc -lm >> >>However, I am getting the
2006 Apr 18
2
[LLVMdev] creating a project from sample project
Thank you for the response. I guess the only thing that is confusing is that the LLVM documentation, at http://llvm.org/docs/Projects.html under the "Create a Project from the Sample Project" heading, indicates that (1) you can place your project *anywhere* you want, and (2) that you are supposed to use the AutoRegen.sh script as is. However, that seems not to be the case. The
2007 Feb 06
1
[LLVMdev] llvm-poolalloc compilation failed
Chris, I performed the steps you gave below to check out llvm-poolalloc. When I want to get new updates made to llvm-poolalloc, do I perform the following commands? cvs -d :pserver:anon at llvm.org:/var/cvs/llvm login <Hit return for an empty password> cd llvm/projects cvs -d :pserver:anon at llvm.org:/var/cvs/llvm update -r release_19 llvm-poolalloc In other words, do I specify the
2007 Apr 10
0
[LLVMdev] cvs opt broken?
This has been reported. http://llvm.org/bugs/show_bug.cgi?id=1317 On 4/10/07, Ryan M. Lefever <lefever at crhc.uiuc.edu> wrote: > > I checked out llvm from cvs & llvm-gcc from svn last night and again > tonight. Each time they compiled and installed fine. After installing > them, I recompiled compiler transforms I had written for opt. opt seems > to load the my
2007 Mar 06
1
[LLVMdev] using dsa
How do I acquire that version of DSA that you've updated to mainline cvs? Do I still check out llvm-poolalloc, or is there a way to only check out DSA? Patrick Meredith wrote: > I updated dsa to mainline cvs. Poolalloc is broken, however. > > On Mar 6, 2007, at 3:39 AM, Ryan M. Lefever wrote: > >> What versions of llvm and llvm-poolalloc should I check out of cvs, in
2007 Apr 09
2
[LLVMdev] llvm/projects
I didn't see anything on http://llvm.org/SVNMigration.html, but I'm assuming that llvm/projects has moved to llvm/examples. Is that correct? If so the documentation in http://llvm.org/docs/GettingStarted.html will need to be updated. In particular, the getting started doc talks about checking out llvm-test to llvm/projects. Also, I'm curious why the llvm/projects/sample
2007 Mar 07
0
[LLVMdev] llvm-ld error
I get a similar error when I try to disassemble a bytecode file generated by llvm-gcc released for llvm 1.9. Do I need to upgrade to a new llvm-gcc? Ryan M. Lefever wrote: > I am trying to use llvm-ld but when I try to link several bytecode files > into a single bytecode file, it gives me the following error: > > llvm-ld -o benchmarks/bc-1.06/src/bc.c.bc
2007 Mar 07
1
[LLVMdev] use of CallInst()
Thanks for the help Reid! I frequently look at the online doxygen, but sometimes its difficult to determine the correct replacement when a method is removed from LLVM. In this particular case, I knew which new CallInst constructor to use, I just couldn't figure out the proper syntax. At any rate, I really appreciate your help!! Reid Spencer wrote: > On Tue, 2007-03-06 at 22:44 -0600,
2006 Apr 19
2
[LLVMdev] creating a project from sample project
Reid, Thanks for the help. I am trying out the fixes you checked into CVS. I seem to be getting some errors running AutoRegen.sh. I am a bit inexperienced with autoconf and m4. The errors I'm getting are below. Do you know what the problem is? I am using machines running FC3. The autoconf version is 2.59, the aclocal version is 1.9.2, and the m4 version is 1.4.1.
2006 Dec 02
3
[LLVMdev] invalid bytecode signature
I am trying to disassemble some bytecode using llvm-dis: llvm-dis -f -o llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc However, I am getting the following error. llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) How do I go about figuring out what the problem is? llvmtest/sliceme2.cbc is newly compiled using the same version of llvm-gcc as llvm-dis. -- Ryan M. Lefever
2007 Feb 22
0
[LLVMdev] opt -verify
I also tried iterating through the functions of the module and calling verifyFunction(), which also returns false, but does not cause an abort or report anything to stderr about what caused the verification to fail. From the doxygen for verifyFunction() and verifyModule(), it seems like they both should print information to stderr if the verification fails and should abort opt if
2007 Apr 12
2
[LLVMdev] compilation failure on OS X powerpc
The reason I didn't use Xcode 2.4 is because I'm running OS X 10.3.9 (Panther). I have not upgraded the OS to 10.4. Xcode 2.4 requires OS X 10.4, according to Apple's website. Do you know otherwise? I think the highest Xcode I can get is 1.5. By the way what does FSF mean? I also tried compiling llvm with the gcc 3.3 that comes with OS X 10.3, and it gave the exact same error