Re: register allocation questions

2004-10-29 Thread Leopold Toetsch
Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Bill Coffman <[EMAIL PROTECTED]> wrote: >> t/library/dumper.t5 1280135 38.46% 1-2 5 8 13 > I didn't look too close, but it's probably only the entry points: > .sub _dumper > _global_dumper() Fixed. leo

Re: register allocation questions

2004-10-29 Thread Leopold Toetsch
Bill Coffman <[EMAIL PROTECTED]> wrote: > Currently, here's how the register allocator is doing. > Failed TestStat Wstat Total Fail Failed List of Failed > --- > t/library/dumper.t5 1280135 38.46%

Re: register allocation questions

2004-10-28 Thread Bill Coffman
Thanks Matt, I hope I can help out. The patch I am submitting actually does simplify register coloring a bit. I've been waiting for perl6 with so much anticipation, I just couldn't stand it any more, and I had to participate. -Bill On Thu, 28 Oct 2004 18:17:57 -0400, Matt Fowles <[EMAIL PROTE

Re: register allocation questions

2004-10-28 Thread Dan Sugalski
At 3:08 PM -0700 10/28/04, Bill Coffman wrote: It passes the other tests, plus the randomized tests that I created, up to 150 symbols. At that range, it still takes about 20x longer than g++ -O2, for equivalent programs to compile (see gen4.pl). Still, that's not bad. Also, it is currently runnin

Re: register allocation questions

2004-10-28 Thread Matt Fowles
Bill~ I have to say that I am really impressed by all of the work that you are doing, and if you can make the internals of imcc a little more approachable, you would be doing a great service. Thanks, Matt On Thu, 28 Oct 2004 15:08:23 -0700, Bill Coffman <[EMAIL PROTECTED]> wrote: > Hi all, > >

Re: register allocation questions

2004-10-28 Thread Bill Coffman
Hi all, Thanks for your continued comments. Btw, I usually read all the parrot list, so don't think I'm not paying attention. Currently, here's how the register allocator is doing. Failed TestStat Wstat Total Fail Failed List of Failed -

Re: register allocation questions

2004-10-28 Thread Dan Sugalski
At 9:36 PM +0200 10/27/04, Leopold Toetsch wrote: Dan Sugalski wrote: At 11:09 AM +0200 10/26/04, Leopold Toetsch wrote: So, if you want that really super efficient, you would allocate registers around function calls directly to that wanted register number, which should be in the SymReg's want_reg

Re: register allocation questions

2004-10-27 Thread Leopold Toetsch
Dan Sugalski wrote: At 11:09 AM +0200 10/26/04, Leopold Toetsch wrote: So, if you want that really super efficient, you would allocate registers around function calls directly to that wanted register number, which should be in the SymReg's want_regno. While true, in the general case leaving 0-15 a

Re: register allocation questions

2004-10-27 Thread Dan Sugalski
At 11:09 AM +0200 10/26/04, Leopold Toetsch wrote: Bill Coffman <[EMAIL PROTECTED]> wrote: > 1) In the existing parrot code, when a register is assigned, it uses the following code: int c = (color + MAX_COLOR/2) % MAX_COLOR; Thus, it seems to prefer to use register #1

Re: register allocation questions

2004-10-26 Thread Leopold Toetsch
Bill Coffman <[EMAIL PROTECTED]> wrote: > Hello All, > I have been hard at work, trying to grok the reg_alloc.c code, and > with some success. My code is assigning registers, so that none are > conflicting (which I double-verify), and I'm getting to the end of > "make". Wow. > 1) In the exist

Re: register allocation questions

2004-10-25 Thread Dan Sugalski
At 6:18 PM -0700 10/25/04, Bill Coffman wrote: Hello All, I have been hard at work, trying to grok the reg_alloc.c code, and with some success. My code is assigning registers, so that none are conflicting (which I double-verify), and I'm getting to the end of "make". Woohoo! A non-trivial thing. :

register allocation questions

2004-10-25 Thread Bill Coffman
Hello All, I have been hard at work, trying to grok the reg_alloc.c code, and with some success. My code is assigning registers, so that none are conflicting (which I double-verify), and I'm getting to the end of "make". Nonetheless, I don't get too far into "make test", and I'm not quite sure w