search for: burge

Chris, Thanks for your answer Here is the verbose output: =========================== gmake tools-only VERBOSE=1 TOOL_VERBOSE=1 for dir in lib/System lib/Support utils lib tools ; do \ if [ ! -f $dir/Makefile ]; then \ /home/myuser/LLVM/objdir/../srcdir/autoconf/mkinstalldirs $dir; \ cp /home/myuser/LLVM/objdir/../srcdir//$dir/Makefile $dir/Makefile; \ fi; \ (gmake -C $dir all )

I found 179 more *.{c,cpp,h} files with tabs. Unfortunately, the tabs stops used vary so blindly expanding them messes up alignment in many cases :( Index: examples/BFtoLLVM/BFtoLLVM.cpp Index: include/llvm/AbstractTypeUser.h Index: include/llvm/GlobalVariable.h Index: include/llvm/InstrTypes.h Index: include/llvm/IntrinsicInst.h Index: include/llvm/ADT/PostOrderIterator.h Index:

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"

There is almost certainly a bug in lnt or the makefiles. I changed the body of Burg main to the following: + printf("Hello World\n"); + return 0; I re-ran the test-suite again and got the following errors: --- Tested: 986 tests -- FAIL: MultiSource/Applications/Burg/burg.execution_time (494 of 986) FAIL: MultiSource/Applications/ClamAV/clamscan.execution_time (495 of 986) FAIL:

Hi These are: ======================== llvm[2]: Linking Release Object Library LLVMbzip2.o gmake[2]: Leaving directory `/homes/myuser/LLVM/llvmobj/lib/Support/bzip2' gmake[1]: Leaving directory `/homes/myuser/LLVM/llvmobj/lib/Support' gmake[1]: Entering directory `/homes/myuser/LLVM/llvmobj/utils' gmake[2]: Entering directory `/homes/myuser/LLVM/llvmobj/utils/Burg' llvm[2]:

Hi, I get the following failures when I run the test-suite on linux (Ubuntu 12.04) using LNT (lnt runtest nt ...): (all are execution failures) MultiSource/Applications/Burg MultiSource/Applications/ClamAV MultiSource/Applications/lemon MultiSource/Applications/obsequi MultiSource/Benchmarks/MiBench/automotive-bitcount

It seems that this happened before but I do not know the details: http://llvm.cs.uiuc.edu/testresults/SparcV9/2004-12-07.html Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > llvm[2]: Compiling zalloc.c for Release build > > /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin > > g types for

Hi Chris, Thanks a lot for your answer! Chris Lattner wrote: >> 1. Why does X86 instruction set description provide different >> descriptions for the same instructions, which differ only in the size >> of operands? >> E.g. >> >> def MOV8rm : I<0x8A, MRMSrcMem, (ops GR8 :$dst, i8mem :$src), >> "mov{b} {$src, $dst|$dst, $src}",

As part of the LLVM build, burg is now built. It is located in llvm/utils/Burg. This is intended to aid development on different build platforms. -Chris http://llvm.cs.uiuc.edu/ http://www.nondot.org/~sabre/Projects/

Burg now uses the same build system as the rest of the llvm system. It sends it's files into the correct BUILD_ROOT, and can build seperate debug, release, and profile versions as well. The only user of burg (lib/Target/Sparc) will automatically use the correct binary from your BUILD_ROOT. This is implemented with the following change sets:

Hi, I figured out how to resolve the failures. I noticed that Mountain Lion includes Bison 2.3 while Ubuntu 12.04 includes Bison 2.5. I installed Bison 2.3 from source in Ubuntu and the failures went away. I'm a little concerned that the bison version fixed all the failures I was seeing. To my knowledge the only failing test that depended on bison was Burg. It almost looks like one failure

I commented this line and it is compiling now: extern void *malloc ARGS((unsigned)); I hope that will not cause a different kind of problem. What it is zalloc used for? Thanks --- Chris Lattner <sabre at nondot.org> wrote: > On Sat, 12 Mar 2005, xavier wrote: > > > It seems that this happened before but I do not know the details: > >

i want to extend a burg-style code generator generator to write a retargetable compiler, implementing the algorithm: Rainer Leupers: Code Selection for Media Processors with SIMD Instructions. DATE 2000: 4-8 what i have now is only iburg, though robust but with very limited functionality. i have consider using "nova" - http://cocom.sourceforge.net/nona.html but it seems not be

On Sun, Jan 20, 2013 at 1:26 PM, Redmond, Paul <paul.redmond at intel.com> wrote: > There is almost certainly a bug in lnt or the makefiles. > > I changed the body of Burg main to the following: > > + printf("Hello World\n"); > + return 0; > > > I re-ran the test-suite again and got the following errors: > > --- Tested: 986 tests -- > FAIL:

It seems awfully tricky to get llvm working on a windows machine. I just want to use the tools, since I want to write my own front end. Here's where I get stuck llvm[2]: Linking Debug executable burg /usr/lib/gcc/i686-pc-cygwin/3.4.1/../../../libstdc++.a: could not read symbols: Archive has no index; run ranlib to add one collect2: ld returned 1 exit status make[2]: ***

On Mon, 2 Oct 2006, Roman Levenstein wrote: >>> Wouldn't it be possible and even more clean to have just one >>> description like (I use a pseudo-description here): >>> >>> def MOVrr : I<0x88, MRMDestReg, (ops (GR8|GR16|GR32) :$dst, >>> (i8mem|i16mem|i32mem):$src), >>> "mov{b} {$src, $dst|$dst, $src}", []>,

> > Are you able to run nightly test ? > Yes, I can run nightly test. > Here is what I see... > > $ make TEST=dbgopt > /Developer/usr/bin//llvm-gcc sse.expandfft.c -g --emit-llvm -c -o > Output/sse.expandfft.bc > /Volumes/Nanpura/mainline/llvm/Debug/bin/opt Output/sse.expandfft.bc - > strip-nondebug -strip-debug -std-compile-opts -strip -f -o Output/ >

The machinery around the bison call in the Makefile does not work for me. From the source file gram.yc, my bison (version 1.28) generates files gram.yc.tab.h and gram.yc.tab.c instead of gram.tab.cc and gram.tab.hc. My fix is to use the -o option to tell bison what to name the outputs. -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part

does anyone knows how to get the Olden BM bytecode files? We're low on disk space and I don't want to build the whole test branch (even if i can, which I doubt, it failed last time i tried).

On Sun, 1 Oct 2006, Roman Levenstein wrote: > I'm trying to implement a new backend for an embedded CISC processor. > Therefore I thought that it makes sense to take X86 target as a basis, > to save some time. Ok. Note that the X86 backend is one of the most complex though, because it supports several subtargets and ABIs, which makes it more complex than some other targets. >