similar to: [LLVMdev] About test suits Cont2

---------- Forwarded message ---------- From: Qingan Li <ww345ww at gmail.com> Date: 2011/1/19 Subject: Re: [LLVMdev] About test suits Cont1 To: Eric Christopher <echristo at apple.com> *I am sorry for making you confused when I presented my problem.* *1. My steps for the test suit building:* (1) cd /home/qali/Src; * // This is my source directory for all application

*1. I have searched the access/setting of LLVMCC_EMITIR_FLAG in the build directory, recursively, and all the output is what I pasted in last email (just the same to the that in source directory). Maybe the configure failed to do it. My command list for building the test suit is as followings:* *(1) cd ~/SRC_DIR/llvm/projects* *(2) svn co http://llvm.org/svn/llvm-project/test-suite/trunk

Hi, I am trying to add a small new backend for LLVM. For assembly printing, I have derived a class from AsmTarget, struct LLVM_LIBRARY_VISIBILITY Asd_ARMAsmPrinter : public AsmPrinter After creating all the bits and pieces, I was trying to use this to print the assembly for a sample program. Though I was getting weird errors. I tried looking for the problem and found that the my target

On Jan 13, 2011, at 6:22 PM, Qingan Li wrote: > make[4]: Entering directory `/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource/UnitTests/Vector/SSE' > /home/qali/Src/llvm-2.8/autoconf/mkinstalldirs Output > /dev/null > /home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc -I/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource/UnitTests/Vector/SSE

[qali at qali test-suite]$ make VERBOSE=1 if [ ! -f SingleSource/Makefile ]; \ then \ /home/qali/Src/llvm-2.8/autoconf/mkinstalldirs SingleSource; \ cp /home/qali/Src/llvm-2.8/projects/test-suite/SingleSource/Makefile SingleSource/Makefile; \ fi; \ make -C SingleSource all make[1]: Entering directory `/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource' if [ ! -f UnitTests/Makefile

*[qali at qali llvm-2.8-rev]$ find . -exec grep -n "LLVMCC_EMITIR_FLAG" ./ {} \;* ./projects/test-suite/Makefile.tests:47: -$(LCC) $(CPPFLAGS) $(CFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG) ./projects/test-suite/Makefile.tests:51: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG)

1. My configuration: OS: ubuntu11.04, CPU: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz llvm: llvm-2.8 2. My running environment: ~#llvm-gcc -DCOMPDATE="today" -DCFLAGS="" -DHOSTNAME="thishost" -DNeedFunctionPrototypes=1 -DSASR -DPROBES=8 -O3 -emit-llvm /home/qali/Develop/Benchmark/MultipleSource/FreeBench/distray/distray.c -o

Please email the list, not me directly. Try doing a 'make clean' then a 'make VERBOSE=1' in the test-suite directory. -Chris On Jan 13, 2011, at 6:04 PM, Qingan Li wrote: > Hi Chris, > > [qali at qali SingleSource]$ llvm-gcc -v > Using built-in specs. > Target: x86_64-unknown-linux-gnu > Configured with: /home/nicholas/2.8-final/llvmgcc42-2.8.src/configure

I have built and configured the test suits as told at http://llvm.org/docs/TestingGuide.html#testsuite. The llvm is built with configuration: SRC_DIR/configure --prefix=INS_DIR --enable-debug-runtime --disable-optimized --enable-debug-symbols --enable-assertions This configuration is used again in the re-configure process. However, after the re-configure process, the following "make"

Hi sir, I have built the test suits in following steps: 0. $cd LLVM_GCC_DIR; $gunzip --stdout llvm-gcc-4.2-*version*-* platform*.tar.gz | tar -xvf - 1. $cd SRC_DIR/llvm-2.8/projects 2. $svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite 3.$cd OBJ_DIR; 4. $SRC_DIR/configure --prefix=INS_DIR --enable-debug-runtime --disable-optimized --enable-debug-symbols

On Jan 15, 2011, at 8:06 PM, Qingan Li wrote: > [qali at qali llvm-2.8-rev]$ find . -exec grep -n "LLVMCC_EMITIR_FLAG" ./ {} \; > ./projects/test-suite/Makefile.tests:47: -$(LCC) $(CPPFLAGS) $(CFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG) > ./projects/test-suite/Makefile.tests:51: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S

I use a 64bit-x86 computer, with Fedora Core 13, and want to build the llvm-gcc. According to the README.LLVM file, I firstly built llvm 2.8 in /home/qali/install/llvm-2.8 using: $./configure $./make ENABLE_OPTIMIZED=1 It succeded. Then, I tried to built llvm-gcc in an 'obj' directory different from the soucre directory, using: $./llvm-gcc-4.2-2.8.source/configure

Pending positive confirmation in http://llvm.org/PR2886, I'd recommend that r57974 and r57976 be pulled into the 2.4 release branch and configure regenerated there. Begin forwarded message: > From: Gordon Henriksen <gordonhenriksen at mac.com> > Date: October 22, 2008 08:40:40 EDT > To: llvm-commits at cs.uiuc.edu > Subject: [llvm-commits] [llvm] r57974 -

I have been working for extending test coverage for years. Nowadays, I have several cross-testing (target != host). See http://bb.pgr.jp/console Each of them (test-*-linux) is doing; - Assume a preceding builder passes with warming ccache. - All compilation units will hit ccache whenever the tree is built before lit. - Almost all compilation units will hit ccache except for Host.cpp when

Getting the following on Cygwin :- Running /home/ang/svn/llvm/test/Bindings/Ocaml/ocaml.exp ... FAIL: /home/ang/svn/llvm/test/Bindings/Ocaml/analysis.ml Failed with exit(2) at line 1 while running: /usr/bin/ocamlc -cc g++ -I /home/ang/build/llvm/Debug/lib/ocaml - warn-error A llvm.cma llvm_analysis.cma /home/ang/svn/llvm/test/Bindings/Ocaml/a nalysis.ml -o analysis.ml.tmp 2> /dev/null child

Gordon Henriksen wrote: > On 2008-06-11, at 13:16, Gary Benson wrote: > > Duncan Sands wrote: > > > Can you please attach IR which can be compiled to an executable > > > (and shows the problem). > > > > I've been generating functions using a builder and then compiling > > them with ExecutionEngine::getPointerToFunction(). Is there some > >

Hello, ogg123 | ices2 are doing transcoding but ogg123 is staying frozen under certain circumstances here is the stack #0 0x401f25d4 in __pthread_sigsuspend () from /lib/libpthread.so.0 #1 0xbffff94c in ?? () #2 0x401f2398 in __pthread_wait_for_restart_signal () from /lib/libpthread.so.0 #3 0x401eef0b in pthread_cond_wait@GLIBC_2.0 () from /lib/libpthread.so.0 #4 0x0804b0d3 in

On Mar 27, 2007, at 3:25 PM, Evan Cheng wrote: > > On Mar 25, 2007, at 7:12 AM, Christopher Lamb wrote: > >> While beginning to add vector registers to a back end I came >> across the following problem: as soon as I define two sets of >> registers that have a many-to-one mapping the live interval pass >> appears to double-kill the mapped-onto register. I

On Apr 3, 2007, at 3:45 PM, Christopher Lamb wrote: > >> Can you dump out the machine basic block? It should have an >> implicit use of V4R0 at first ORI but it should not be marked kill. >> If it is marked kill, then you need to walk LiveVariables.cpp to >> find out why. > > Here is the beginning of the BB dump. > > entry (0x8503c80, LLVM BB @0x8501af0,

On Tue, 01 May 2012 21:25:29 -0500 Peter Bergner <bergner at vnet.ibm.com> wrote: > On Tue, 2012-05-01 at 19:58 -0500, Peter Bergner wrote: > > On Tue, 2012-05-01 at 17:47 -0500, Hal Finkel wrote: > > > By default it should build for > > > whatever the current host is (no special flags required). To > > > specifically build for something else, use: