similar to: [LLVMdev] RE: Ticket #7559: FW: Bradfields/PCJF-10959

Great! Could you please add a /localhome directory to each of them? Since there are 2 disks per machine, perhaps the best thing to do would to make /localhome a real directory and make separate local directories on each disk, so that we can each do something like this: /localhome/vadve -> /mounts/seraph/disks/0/localhome/vadve /localhome/lattner ->

On Mon, 7 Nov 2005, Bill Wendling wrote: > What's the config.log from this run? its attached. -Tanya > > -bw > > On 11/3/05, Tanya Lattner <tonic at nondot.org> wrote: >> >> Following the instructions here: >> http://llvm.cs.uiuc.edu/docs/TestingGuide.html#run >> >> I get an error running configure in the llvm-test directory. >>

Rahul, Were you talking about tracing in the sense of "profiling" (which Anand did), or tracing of values as they are computed for debugging generated code (which I did)? For tracing of values for debugging, the answer is yes: we insert code in each BB and print out the values computed in that BB that are live at the end of the BB (so we don't print out temporaries computed and

Following the instructions here: http://llvm.cs.uiuc.edu/docs/TestingGuide.html#run I get an error running configure in the llvm-test directory. ./configure --with-llvmgccdir=/localhome/tbrethou/cfrontend/sparc/llvm-gcc/ --with-f2c=/home/vadve/shared/localtools/sparc --with-llvmsrc=/localhome/tbrethou/llvm --with-llvmobj=/localhome/tbrethou/llvm Error: [cut lots of config output] checking

Tanya Lattner wrote: > > Following the instructions here: > http://llvm.cs.uiuc.edu/docs/TestingGuide.html#run > > I get an error running configure in the llvm-test directory. > > ./configure > --with-llvmgccdir=/localhome/tbrethou/cfrontend/sparc/llvm-gcc/ > --with-f2c=/home/vadve/shared/localtools/sparc > --with-llvmsrc=/localhome/tbrethou/llvm >

What's the config.log from this run? -bw On 11/3/05, Tanya Lattner <tonic at nondot.org> wrote: > > Following the instructions here: > http://llvm.cs.uiuc.edu/docs/TestingGuide.html#run > > I get an error running configure in the llvm-test directory. > > ./configure > --with-llvmgccdir=/localhome/tbrethou/cfrontend/sparc/llvm-gcc/ >

I'm encountering a new problem building llvm (from CVS) on Solaris. The tblgen executable builds successfully but it seems to use the wrong version of libstdc++ : % /home/vadve/vadve/llvm-sparc/Debug/bin/tblgen --help ld.so.1: /home/vadve/vadve/llvm-sparc/Debug/bin/tblgen: fatal: /home/ vadve/lattner/local/x86-fc1/gcc-3.4.2/lib/libstdc++.so.6: wrong ELF class: ELFCLASS32 Killed This

----- Original Message ----- From: "Chris Lattner" <sabre at nondot.org> To: <llvmdev at cs.uiuc.edu> Sent: Wednesday, June 23, 2004 4:05 PM Subject: Re: [LLVMdev] weird issue with mem2reg > On Wed, 23 Jun 2004, Patrick Meredith wrote: > > > MetaSplit is an anlysis I just finished writing. It doesn't alter anything, > > all it does is build a set of

MetaSplit is an anlysis I just finished writing. It doesn't alter anything, all it does is build a set of "program instructions". For some reason even though if I run it with any other combination of passes I've found, anytime I run it with mem2reg I get a seg fault in dyn_cast! Here's output: Starting program: /mounts/zion/disks/0/localhome/pmeredit/llvm/tools/Debug/opt

On Wed, 23 Jun 2004, Patrick Meredith wrote: > MetaSplit is an anlysis I just finished writing. It doesn't alter anything, > all it does is build a set of "program instructions". For some reason even > though if I run it with any other combination of passes I've found, anytime > I run it with mem2reg I get a seg fault in dyn_cast! Here's output: > >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all. Yesterday I updated my version of wine from cvs. Now, when I try to compile I receive a signal 11 error. The message is as follows: make[2]: Leaving directory `/localhome/emmebi/wine/dlls/lzexpand' make[2]: Entering directory `/localhome/emmebi/wine/dlls/version' make[2]: `libversion.so' is up to date. make[2]: Leaving

Compiling llvm-gcc on an x86 machine with --target=powerpc-ibm-aix5.1.0.0, I get the following error: make \ CFLAGS="-g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute " \ CONFIG_H="config.h auto-host.h

Linking lli debug executable (without symbols) /mounts/zion/disks/0/localhome/pmeredit/llvm/lib/Debug/lli-interpreter.o(.te xt+0x643a): In function `llvm::Interpreter::callExternalFunction(llvm::Function*, std::vector<llvm::GenericValue, std::allocator<llvm::GenericValue> > const&)': /localhome/pmeredit/llvm/lib/ExecutionEngine/Interpreter/ExternalFunctions.c pp:98: undefined

Do something like this: bugpoint -run-llc <bitcode file> --tool-args -- <llc arguments> Cameron On May 23, 2011, at 1:33 PM, Arushi Aggarwal wrote: > Hi, > > What is the best way to debug an llc crash using bugpoint? > > I am getting the following crash that I would like to reduce > > llc: /home/vadve/aggarwa4/llvm29/llvm-2.9/lib/MC/MCAsmStreamer.cpp:273:

Hi, What is the best way to debug an llc crash using bugpoint? I am getting the following crash that I would like to reduce llc: /home/vadve/aggarwa4/llvm29/llvm-2.9/lib/MC/MCAsmStreamer.cpp:273: virtual void<unnamed>::MCAsmStreamer::EmitLabel(llvm::MCSymbol*): Assertion `Symbol->isUndefined() && "Cannot define a symbol twice!"' failed. 0 llc

This email isn't really LLVM specific, but is definately useful for LLVM people so.... I've downloaded and installed "valgrind" (http://developer.kde.org/~sewardj/), an open source "purify" replacement. It is actually quite a bit nicer than purify is, as it doesn't require you to recompile or modify your executables _at all_ to run them (it also seems quite fast).

Hi Patrick, You need to modify your makefile for building your version of lli so that it includes the LLVMBCWriter.o library. You can do this with a line like: LLVM_LIBS=LLVMBCWriter if you're using the LLVM Makefile system. Otherwise you just need to make sure that {Debug,Release}/lib/LLVMBCWriter.o gets added to the link line. Reid. On Thu, 2005-02-24 at 16:37, Patrick Meredith wrote:

I didn't 'cause my llvm-gcc just seems to be 4.0: ]$ llvm-gcc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../llvm-gcc4-1.9.source/configure --prefix=/mounts/zion/disks/0/localhome/tbrethou/llvm-gcc4/obj/../install --enable-llvm=/localhome/tbrethou/llvm --enable-languages=c,c++ --disable-threads Thread model: single gcc version 4.0.1 LLVM (Apple Computer, Inc. build

Dear LLVM developers, I am pleased to announce that the autoconf support has been added to mainline CVS. This addition allows the LLVM build environment to be configured via the familiar configure script. The autoconf support might have some bugs in it, so please report them if you see them. Also be warned that many files have changed to use header files that wrap the autoconf

Hi all, I am a newbie to LLVM and tried experimenting compile a small C program with it. This is what I did: 1. Wrote a simple C program with some dead code. 2. compiled it with llvm-gcc. [$ llvm-gcc -emit-llvm -S deadc.c] 3. Fetched it to assembler. [$ llvm-as deadc.s] 4. [$ opt -analyze -ade deadc.s.bc] [Ran without -analyze switch also: $opt -o final_opt -verify-each -globaldce -f deadc.s]