search for: burg

.../objdir/lib/Support/bzip2' gmake[2]: Nothing to be done for `all'. gmake[2]: Leaving directory `/home/myuser/LLVM/objdir/lib/Support/bzip2' gmake[1]: Leaving directory `/home/myuser/LLVM/objdir/lib/Support' gmake[1]: Entering directory `/home/myuser/LLVM/objdir/utils' for dir in Burg TableGen fpcmp; do \ if [ ! -f $dir/Makefile ]; then \ /home/myuser/LLVM/objdir/../srcdir/autoconf/mkinstalldirs $dir; \ cp /home/myuser/LLVM/objdir/../srcdir/utils/$dir/Makefile $dir/Makefile; \ fi; \ (gmake -C $dir all ) || exit 1; \ done gmake[2]: Entering directory `/home/myuser/L...

.../SparcV8/SparcV8TargetMachine.cpp Index: lib/Target/SparcV9/EmitBytecodeToAssembly.cpp Index: lib/Target/SparcV9/MachineFunctionInfo.cpp Index: lib/Target/SparcV9/MachineFunctionInfo.h Index: lib/Target/SparcV9/MappingInfo.cpp Index: lib/Target/SparcV9/MappingInfo.h Index: lib/Target/SparcV9/SparcV9BurgISel.cpp Index: lib/Target/SparcV9/SparcV9FrameInfo.h Index: lib/Target/SparcV9/SparcV9InstrForest.h Index: lib/Target/SparcV9/SparcV9Internals.h Index: lib/Target/SparcV9/SparcV9PrologEpilogInserter.cpp Index: lib/Target/SparcV9/SparcV9RegClassInfo.cpp Index: lib/Target/SparcV9/SparcV9RegClassInfo....

...igure process, the following "make" failed: qali at qali MultiSource]$ make make[1]: Entering directory `/home/qali/build/llvm-2.8-rev/projects/test-suite/MultiSource/Applications' make[2]: Entering directory `/home/qali/build/llvm-2.8-rev/projects/test-suite/MultiSource/Applications/Burg' /home/qali/build/llvm-2.8-rev/Debug+Asserts/bin/llvm-as Output/be.ll -o Output/be.bc /home/qali/build/llvm-2.8-rev/Debug+Asserts/bin/llvm-as: Output/be.ll:1:2: error: expected top-level entity .file "/home/qali/Src/llvm-2.8/projects/test-suite/MultiSource/Applications/Burg/be.c" ^ ma...

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

...rary 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]: Compiling be.c for Release build llvm[2]: Compiling burs.c for Release build llvm[2]: Compiling closure.c for Release build llvm[2]: Compiling delta.c for Release build llvm[2]: Compiling fe.c for Release build llvm[2]: Compiling gram.tab.c for Release build /usr/lib/bison.simple: In...

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 MultiSource/Benchmarks/MiBench/telecomm-FFT MultiSource/Benchmarks/Olden/...

...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 'malloc' > > /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin > > g types for 'malloc' > > gmake[2]: *** [/homes/myuser/LLVM/llvmobj/utils/Burg/Release/zalloc.o] Error 1 > > gma...

.... Thanks a lot for explanations. Multiclasses seem to provide almost everything (if not all) of the features that I was asking for. I'll try to use it for writing a short and concise definition of instructions for my target. >> 2. Another related question is about instruciton costs. In BURG-based >> selectors there is usually a possibility to describe costs for the >> instructions so that a least-cost cover can be found during the >> instruction selection process. I have not seen any such cost >> descriptions in TableGen files. Does it mean that it is not suppo...

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

...at 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 can cause unrelated tests to fail. Any ideas? paul On 2013-01-17 5:24 PM, "Redmond, Paul" <paul.redmond at intel.com> wrote: >Hi, > >I get the following failures when I run the test-suite on linux (Ubuntu >12.04) using LNT (lnt runte...

...eek-of-Mon-20041213/022366.html > > -Chris > > > > --- 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 'malloc' > >>> /homes/myuser/LLVM/llvmobj/../llvmsrc/utils/Burg/zalloc.c:9: error: conflictin > >>> g types for 'malloc' > >>> gmake[2]: *** [/homes/myuser/LLVM/llvmobj/utils/Burg/Release...

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

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: MultiSource/Applications/Burg/burg.execution_time (494 of 986) > FAIL: MultiSource/App...

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]: *** [/usr/src/llvm/Debug/bin/burg.exe] Error 1 make[2]: Leaving directory `/usr/src/llvm/utils/Burg' make[1]: *** [all] Error...

...gt; shouldn't need to do this, except in extreme cases. Are you seeing > cases >> where the selector is missing an optimal match, or are you just used > to >> other tools which aren't as smart at inferring cost as tblgen? > > I guess, I'm just used to other more BURG-like tools. And yes, they are > not too intelligent compared to tblgen;) ok. > So far, I haven't seen a real case where an optimal match is missed by > tblgen. But I have not completely converted the old BURG-spec into > tblgen yet. When I'm ready, I'll try to compare the...

...mobj/projects/llvm-test/MultiSource' make[2]: Entering directory `/developer/home2/zsth/projects/llvm.org/build/llvmobj/projects/llvm-test/MultiSource/Applications' make[3]: Entering directory `/developer/home2/zsth/projects/llvm.org/build/llvmobj/projects/llvm-test/MultiSource/Applications/Burg' make[3]: *** No rule to make target `Output/burg.diff', needed by `test.dbgopt.burg'. Stop. make[3]: Leaving directory `/developer/home2/zsth/projects/llvm.org/build/llvmobj/projects/llvm-test/MultiSource/Applications/Burg' make[2]: *** [Burg/.maketest] Error 2 make[2]: Leaving dir...

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

...2 :$dst, i32mem:$src) > { > "$assm_op{l} {$src, $dst|$dst, $src}", > [(set GR32:$dst, ($insn_effect_op GR16:$dst, (load addr:$src)))] > > }; Yep. tblgen gives you lots of tools to factor your instructions. > 2. Another related question is about instruciton costs. In BURG-based > selectors there is usually a possibility to describe costs for the > instructions so that a least-cost cover can be found during the > instruction selection process. I have not seen any such cost > descriptions in TableGen files. Does it mean that it is not supported? LLVM curr...