similar to: [LLVMdev] llvm installation failure

I checked llvm-gcc 4.0 out from svn yesterday and am compiling it on 3 different machines. I was able to compile it on 2 of the machines, but the compilation failed on the third machine with the errors below. The machine that the compilation failed on is running Fedora Core 4. The processor is a AMD Athlon(tm) 64 Processor 3700+. The version of gcc I have on the machine is 4.0.2. I tried

On Wed, 22 Aug 2007, Ryan M. Lefever wrote: > I checked llvm-gcc 4.0 out from svn yesterday and am compiling it on 3 > different machines. I was able to compile it on 2 of the machines, but > the compilation failed on the third machine with the errors below. The > machine that the compilation failed on is running Fedora Core 4. The > processor is a AMD Athlon(tm) 64 Processor

Chris, I'm a little confused. I am experiencing a crash when compiling the llvm-gcc frontend. According to the bugpoint documentation, bugpoint is used to debug "optimizer crashes, miscompilations by optimizers, or bad native code generation," which seems like it implies that the frontend compiles. Also, the http://llvm.org/docs/HowToSubmitABug.html documentation seems to

Command from LLVM CFE bootstrap sequence at FreeBSD: gmake -C runtime install-bytecode terminated with error (verbose mode): --8X------------------------------------------------------- llvm[2]: Installing Debug Bytecode Archive /usr/home/wanderer/pkg/build/llvm/night/cfe/bin/../lib/libcrtend.a /usr/bin/install -c -D /usr/home/wanderer/pkg/build/llvm/obj/Debug/lib/libcrtend.bca

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

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 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 following assertion failure in llc. The bytecode has been processed with opt, it passes opt bytecode verification. I'm not too familiar with backend code generation. Does anyone have any insight in to what the problem might be or how to go about

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 following assertion failure in llc. The > bytecode has been processed with opt, it passes opt bytecode > verification. I'm not too familiar with backend

When I use LLVM to translate bytecode to C, it seems to stick its own definitions of several glibc calls like strcpy, strcmp, etc, but not others like printf. Is this because strcpy and strcmp have been compiled with llvm and printf has not? Regards, Ryan -- Ryan M. Lefever [217.333.7231] [http://www.ews.uiuc.edu/~lefever]

Vladimir, Thanks for the note. Unfortunately, the install approach that we're using in the makefiles is a bit broken, based on Linux install program. We'll get this cleaned up soon so that it works on multiple unixes. Reid. On Thu, 2005-02-17 at 14:48, Vladimir Merzliakov wrote: > Command from LLVM CFE bootstrap sequence at FreeBSD: > gmake -C runtime install-bytecode >

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

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 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

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 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

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

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

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,

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 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