Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] BigBlock register allocator"
2007 Jun 22
0
[LLVMdev] BigBlock register allocator
Hi Duraid,
> Hi everyone,
>
> Quick summary:
>
> LLVM now has a new register allocator particularly suitable for
> compiling (very) large, machine-generated functions.
Congrats! Very good job!
> Longer story:
>
> I've recently been using LLVM in an application that involves JITing
>
> fairly large functions that have no control flow - they're
2007 Jun 22
1
[LLVMdev] BigBlock register allocator
Hi Roman,
> True. I'm working on the version of the linear scan based on Wimmer's
> thesis. It supports live range splitting. I'd like to compare it with
> yours. Do you have any good examples of those fairly large functions
> that are just flat sequences of instructions, anywhere from 100 to
> 10000+ in size???
You can find a couple attached to bug #1512, but I'm
2009 Jul 30
1
[LLVMdev] Removing the bigblock register allocator.
On Jul 29, 2009, at 10:31 PM, Roman Levenstein wrote:
> As far as I know, we have these ambitious plans since a while (just X
> years), but there is no good replacement for a LLVM linear scan yet :)
> The alternatives are either slower at compile time or generate
> slower code.
Sure, we've been able to make the current algorithm significantly
better over the years. However,
2009 Jul 29
0
[LLVMdev] Removing the bigblock register allocator.
Hi Lang,
There are at least two projects that were using BigBlock, directly or
indirectly.
One approach is described in the paper "Register Spilling and
Live-Range Splitting for SSA-Form Programs" by Matthias Braun and
Sebastian Hack.
It can be found here:
http://pp.info.uni-karlsruhe.de/publication.php?id=braun09cc
http://pp.info.uni-karlsruhe.de/uploads/publikationen/braun09cc.pdf
2009 Jul 29
3
[LLVMdev] Removing the bigblock register allocator.
On Jul 29, 2009, at 3:14 PM, Roman Levenstein wrote:
> Hi Lang,
>
> There are at least two projects that were using BigBlock, directly or
> indirectly.
Hi Roman,
We have many plans to rip out linscan and replace it with something
that handles large blocks better. That's not the issue :). The
problem is that bigblock is unmaintained and bitrotted. Since noone
is working
2009 Jul 30
0
[LLVMdev] Removing the bigblock register allocator.
Hi Chris,
2009/7/30 Chris Lattner <clattner at apple.com>:
>
> On Jul 29, 2009, at 3:14 PM, Roman Levenstein wrote:
>
>> Hi Lang,
>>
>> There are at least two projects that were using BigBlock, directly or
>> indirectly.
>
> Hi Roman,
>
> We have many plans to rip out linscan and replace it with something
> that handles large blocks better.
2009 Jul 29
2
[LLVMdev] Removing the bigblock register allocator.
Hi all,
I'd like to kill off the bigblock register allocator. Is anyone still using it?
Cheers,
Lang.
2007 Oct 05
1
[LLVMdev] Supporting pre-allocated registers in LLVM
> > 1. I can see the standard algorithms (bigblock, linearscan -- good
> > choice for
> > the JIT and for general use as well, and the other algorithms). Is
> > it possible
> > to pre-allocate registers in your linearscan (or in another
> > allocation engine)
> > for specific source-level or (better) intermediate code (bitcode)
> > level
> >
2009 Jul 30
1
[LLVMdev] Removing the bigblock register allocator.
Hi Roman,
> BTW, the research papers that I mentioned are not about improving
> register allocation for large blocks (which was the target in the case
> of BigBlock). They are about register allocation for general purpose
> CFGs. And they report improvements (greatly reduced number of
> load/stores for spills) over linear scan. The compilation time is also
> comparable with
2007 Oct 05
3
[LLVMdev] Supporting pre-allocated registers in LLVM
Hi there
i would like to ask a few questions to the developers responsible for the
register allocator(s) design in LLVM (Fernando and other people).
First of all, congrats on providing more than one option for register
allocation.
Now to the questions:
1. I can see the standard algorithms (bigblock, linearscan -- good choice for
the JIT and for general use as well, and the other algorithms).
2008 Nov 14
0
[LLVMdev] Proper arguments for -march?
Hello,
On Fri, Nov 14, 2008 at 6:57 PM, H. Johnson <misc at faradayco.com> wrote:
> llc -march=x86 tempfileB.bc yields:
> llc: for the -march option: : Cannot find option named 'x86'!
Run llc -help and see, if any backends were linked in. It will show
you list of all backends, which were 'registered' and thus known to
llc.
--
With best regards, Anton Korobeynikov
2008 Nov 14
4
[LLVMdev] Proper arguments for -march?
llc -march=x86 tempfileB.bc yields:
llc: for the -march option: : Cannot find option named 'x86'!
Windows build using Visual Studio 2008 Express with CMake.
clang and other tools seem to also complain about the format of -march,
but other command line arguments seem to be working. Tools, clang
llvm-as, opt, etc., "seem" to be working.
Incidently, the bytecode file was
2007 Dec 13
1
[LLVMdev] Puzzle solver on LLVM 2.1
Dear guys,
I've put the puzzle solver running on LLVM 2.1. Well, at least
partially, for it is failing three of SPEC2000 benchmarks. I will try to
debug it now. The results are not as good as before. I mean, the puzzle
solver is still the same, but the default allocator is producing very good
code now. Even though, the puzzle solver produces faster code for half the
benchmarks. It
2006 Sep 01
3
[LLVMdev] Testing a register allocator
Hi!
I developed a register allocator within LLVM and now I need to test its
efficiency. Can I do this using llvm-test package?
Do llvm tests check all available regalloc options automatically? If not,
then what modifications should I do to the test files?
It would be great if I could test my algo along with linearscan and compare
the results.
Thanks.
Tony.
--
"Nae king! Nae quin! Nae
2006 Sep 02
0
[LLVMdev] Testing a register allocator
> Hi!
>
> I developed a register allocator within LLVM and now I need to test its
> efficiency. Can I do this using llvm-test package?
> Do llvm tests check all available regalloc options automatically? If not,
> then what modifications should I do to the test files?
> It would be great if I could test my algo along with linearscan and compare
> the results.
>
>
2004 Jul 30
3
New to IP-PBX
Hi,
I'd really appreciate it if you can explain this to me.
I have a D/41JCT-LS Dialogic board and I want to use it as an IP-PBX.
I'm new to IP Telephony and telephony and general and I researched a lot
but still confused about what I really need.
I know that I can setup an IP-Telephony for my LAN using a SIP server
and SIP compatible software phones. But the challenge is how can I
2005 Sep 16
2
[LLVMdev] Problems Cross Compiling for x86 and ia64
Hi, I'm having some problems cross-compiling from ppc (OS X) to x86
object files and to ia64, at all. I'd appreciate some advice as to
whether or not I'm actually supposed to be able to do this, and what's
wrong if so.
Here's how I configured it:
../llvm-darcslocal/llvm/configure --with-llvmgccdir=$LLVMGCCDIR
--prefix=$HOME/Documents/hpcl/LLVM/install
The results work fine
2005 Apr 10
1
Fwd: Re: [LLVMdev] new IA64 backend
Does anybody know if there is some tool to convert from WHIRL to LLVM? maybe some project under
development? a similar project?
Thanks
>
> --- Duraid Madina <duraid at octopus.com.au> wrote:
> > Date: Fri, 18 Mar 2005 12:45:54 +0900
> > From: Duraid Madina <duraid at octopus.com.au>
> > To: ahs3 at fc.hp.com, LLVM Developers Mailing List <llvmdev at
2004 Nov 30
2
[LLVMdev] dejagnu tester
Hi all,
This is just to announce that I have a FreeBSD x86 machine running the
test suite more or less continuously:
http://kinoko.c.u-tokyo.ac.jp/~builddonkey/
Of note is that it now runs Dejagnu tests. (Thanks, tonic+co!) I'm also
tracking CVS breakage (internally, for now). At some later point, I'll
make available more real-time information on "is CVS alive and if not,
2005 Mar 17
4
[LLVMdev] new IA64 backend
Hi everyone,
I've just checked in an IA64 backend to LLVM! Be warned, it's pretty
rough right now. Here are some of the known defects:
- No varargs
- No alloca
- No instruction scheduling/bundling of any sort
...or in other words, it breaks often and when it does work, it's a
dog. On the plus side, it _does_ have a tasty new pattern instruction
selector. :) Beyond fixing the