750 - Segmentation fault
r31800 - Segmentation fault
r31900 - Segmentation fault
r32951 - Runs slow - 6min 17sec
I hope this helps
luben
in the PIR you
generate.
(pmichaud, i hope i explained this right! ;-)
-jeff
Thanks, I see now what is the difference. Probably we could optimize out
the explicit returns when we reach the "optimization" phase of the
project.
Best regards
luben
Will Coleda wrote:
On Tue, Aug 26, 2008 at 10:53 AM, luben <[EMAIL PROTECTED]> wrote:
Is this on purpose? The implicit return is 4-5 times faster than explicit
return.
Best regards
luben
CC'ing perl6-compiler (where rakudo-particular items should go), and
wondering if you can
Will Coleda wrote:
On Tue, Aug 26, 2008 at 10:53 AM, luben <[EMAIL PROTECTED]> wrote:
I have noticed that Rakudo (and NQP) generates different PIR code for
implicit and explicit returns.
Example for implicit return:
sub foo($n){
$n;
}
And example for explicit return:
sub foo($n){
return.
Best regards
luben
just replaces
"string_from_literal" with "const_string" on one line. I thought that
const_string is faster because it doesn't need to allocate memory and
produces less garbage. But it happens that it is a lot slower - it adds
11 seconds to the execution (with GC enabled).
Best regards
luben
ere is it source of the bug - the addition op that
produces Num, not Int or the type check.
Luben
