Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
perl.perl6.internals
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Are we done with big changes?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Leopold Toetsch  
View profile  
 More options Nov 5 2004, 2:35 am
Newsgroups: perl.perl6.internals
From: l...@toetsch.at (Leopold Toetsch)
Date: Fri, 5 Nov 2004 08:35:02 +0100
Local: Fri, Nov 5 2004 2:35 am
Subject: Re: Are we done with big changes?
Print | View thread | Show original | Report this message | Find messages by this author

Dan Sugalski <d...@sidhe.org> wrote:
> At 4:38 PM -0500 11/4/04, Matt Diephouse wrote:
>>On Tue, 2 Nov 2004 13:35:09 -0500, Dan Sugalski <d...@sidhe.org> wrote:
>>>  What, think this warrants a 0.1.2 release? I'm not so sure about
>>>  that. It's not that big a deal...

>>In the past week, Parrot has seen a dramatic speedup. We're in about
>>the best shape we've been in in the past 4 months:

>>  http://www.sidhe.org/~timeparrot/graphs/A/sum.png

>>Seems like a pretty big deal.

Raw function calling speed demonstrated by {oo,}fib [1] isn't there, where
it should. But fixing this needs some bigger changes. Anyway I'm glad
that the numbers indicate that the indirect register addressing is the
way to go.

[1] AFAIK a non-recursive benchmark is missing. Is it possible to get
timings for older versions for 3 TODO benchmarks:

Calling some nested functions and returning 1 result repeatedly. One for
PMC-only args/returns, one for int, and one for all 4 kinds of registers.

> Hrm. Okay, then, if I've not managed to make a mess of things with
> the stuff I've been doing, why don't we do a 0.1.2 performance
> release? Between the speedups and the gentler effects of -t it seems
> likely to be worth it for people who're working with parrot to do
> stuff.

Or wait for the new register allocator?

leo


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google