similar to: [LLVMdev] makefile commands

> When using the makefiles in LLVM, the commands that Make executes are > hidden from the user. Instead something like: > > llvm[3]: Compiling Reg2Mem.cpp for Debug build > > is printed to the terminal, rather than the commands that are used to > build Reg2Mem.cpp. Is there a way to get the makefiles to print the > commands that they are executing? VERBOSE=1 -Tanya

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 transform libraries fine, but it complains: opt: Unknown command line argument '-mytransform' whenever I try to specify one of my transforms on the opt

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

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]: ***

Forgot to hit "Reply All." -- John T. -------------- next part -------------- An embedded message was scrubbed... From: John Criswell <criswell at cs.uiuc.edu> Subject: Re: using dsa Date: Tue, 06 Mar 2007 09:53:43 -0600 Size: 3103 URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070306/ef7c2f29/attachment.mht>

How is c's const keyword translated when compiling c into llvm bytecode. I'm specifically interested in const pointer function arguments. Consider a function declared as follows in c: void f(const int* arg); When I examine f in llvm bytecode, how can I tell that arg is a pointer, whose contents can only be read, not written. Regards, Ryan

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

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

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

Nick Lewycky <nicholas <at> mxc.ca> writes: > > Pedro Ferreira wrote: > > Hello, > > > > I am trying to write a LLVM backend for a school project using only > > custom code (as with the CBackend) and I'm having difficulties > > handling the PHI nodes from LLVM asm code. Is there any pass we can do > > before my custom Module Pass to

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

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 > order to use DSA? In a previous post John Criswell suggested checking > llvm and llvm-poolalloc out of cvs using the -r release_19 flag. > However, there were several post later that said that

Hi Ryan, On Fri, 2006-12-01 at 18:06 -0600, Ryan M. Lefever wrote: > 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) The problem is most likely that sliceme2.cbc is *not* bytecode. Open the

What versions of llvm and llvm-poolalloc should I check out of cvs, in order to use DSA? In a previous post John Criswell suggested checking llvm and llvm-poolalloc out of cvs using the -r release_19 flag. However, there were several post later that said that changes should not be made to the release_19 branch. At any rate, I've not seen any update on which versions of llvm and

I followed what you said and called verifyModule() with the AbortProcessAction option. verifyModule() returns false, but does not abort and does not print out any information about what caused the verification to fail. Chris Lattner wrote: > On Wed, 21 Feb 2007, Ryan M. Lefever wrote: >> I am writing an interprocedural compiler pass. Because the passneeds >> information from a

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 benchmarks/bc-1.06/src/bc.i.bc benchmarks/bc-1.06/src/execute.i.bc benchmarks/bc-1.06/src/getopt1.i.bc benchmarks/bc-1.06/src/getopt.i.bc benchmarks/bc-1.06/src/global.i.bc benchmarks/bc-1.06/src/load.i.bc

I am writing a transformation that needs to add a call to a function F() at the beginning of main() with the addresses of argc and argv as parameters to F(). However, the bytecode file I'm transforming has not allocated space on the stack for argc and argv. So, I developed my transformation to change main() from: ----- int main(int %argc, sbyte** %argv){ entry: ... // some use of

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

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

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]