[perl #132306] [PERF] parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

And not only parameters, but unused variables also: https://github.com/rakudo/rakudo/blob/ebb0521bd259e9f81e4b127527534090969f398e/src/core/native_array.pm#L1399 On 2017-10-14 20:53:03, alex.jakime...@gmail.com wrote: > FWIW I made a throwaway script that looks for unused params, and there > are

[perl #132306] [PERF] parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

FWIW I made a throwaway script that looks for unused params, and there are many of these in rakudo sources. Of course, most of these cases are not in hot paths, but the overall performance benefit may be very noticeable. There are also cases like this:

[perl #132306] [PERF] subroutine parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

Oh, I guess it applies to methods as well. On 2017-10-14 20:10:15, alex.jakime...@gmail.com wrote: > Code: > sub f1($a, $, $, $, $, $) { 1 }; > my $s; > $s += f1($_, $_, $_, $_, $_, $_) for ^1_000_000; > say now - BEGIN now > > Result: > 0.43209886 > > > Code: > sub f2($a, $b1, $b2, $b3, $b4,

[perl #132306] [PERF] subroutine parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132306] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132306 > Code: sub f1($a, $, $, $, $, $) { 1 }; my $s; $s += f1($_, $_, $_,

[perl #129790] [OPTIMIZER] Giving a sub to a map fails

Maybe it is worth noting that this is pretty much a regression (even though an old one, and caused by a non-optimizer change). (2016-08-09) https://github.com/rakudo/rakudo/commit/328402599c16077e182bb38baf68e435b8bc1082 Output before and after:

[perl #132305] [UNI] In some cases ‘Numeric’ uniprop returns “Lower” but it should be “None” instead (say ‘a’.uniprop(‘Numeric’))

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132305] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132305 > Code: say ‘a’.uniprop(‘Numeric’) Result: Lower It fluctuates a

[perl #131515] [BISECTME][PERF] Performance loss in some commits

So it *is* the commit originally found, but the Exception.message call was later optimized away to being called only when needed, and not when the exception is thrown, so this don't matter anymore. Commit timing results: https://irclog.perlgeek.de/perl6-dev/2017-10-14#i_15303228

[perl #131515] [BISECTME][PERF] Performance loss in some commits

So it *is* the commit originally found, but the Exception.message call was later optimized away to being called only when needed, and not when the exception is thrown, so this don't matter anymore. Commit timing results: https://irclog.perlgeek.de/perl6-dev/2017-10-14#i_15303228

[perl #132012] [ANNOYING] Numeric values of signals are wrong (say +SIGUSR1)

Someone asked why this issue is ANNOYING, here's some clafirication. Basically, most of the stuff said said in linked comment applies here as well: https://rt.perl.org/Ticket/Display.html?id=131003#txn-1496218 In other words, *some* signals have correct values and you don't notice the issue

Re: [perl #132302] Str.trans grabs callers $/ for unknown reason

On Sat, Oct 14, 2017 at 1:15 PM, Zoffix Znet wrote: > 2) Why does Str.trans grabs caller's $/ in the first place? The commit > that added >it seems to claim to fix something that isn't meant to work as tr/// > replaces per >char and doesn't use special regex

Re: [perl #132302] Str.trans grabs callers $/ for unknown reason

On Sat, Oct 14, 2017 at 1:15 PM, Zoffix Znet wrote: > 2) Why does Str.trans grabs caller's $/ in the first place? The commit > that added >it seems to claim to fix something that isn't meant to work as tr/// > replaces per >char and doesn't use special regex

Re: Perl6 on USB key?

In theory it shouldn't be a problem. If you're mutating files though be aware of the line ending differences between the OS's. But yeah, with only a few gotchas, that shouldn't be a problem. I've been using bash on Windows to write code on my windows partition without any real issues and this

Re: Perl6 on USB key?

Hi Chris, thanks for your feedback. Can you plug the Pi Zero converted to an USB stick into a Windows machine and run Perl6 scripts residing on the latter? > Le 14 oct. 2017 à 18:22, Chris Ramsey a écrit : > > Not really, unless you're just adding the binary and

[perl #132302] Str.trans grabs callers $/ for unknown reason

# New Ticket Created by Zoffix Znet # Please include the string: [perl #132302] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132302 > IRC: https://irclog.perlgeek.de/perl6-dev/2017-10-14#i_15302654 1) Spotted that

[perl #132295] [REGRESSION][LTA] :2(…) radix syntax no longer suggests using .base (:2(42))

On Sat, 14 Oct 2017 00:54:02 -0700, alex.jakime...@gmail.com wrote: > Code: > say :2(1); > > > ¦«2015.12»: > This call only converts base-2 strings to numbers; value 1 is of type > Int, so cannot be converted! > (If you really wanted to convert 1 to a base-2 string, use 1.base(2) > instead.) >

[perl #132295] [REGRESSION][LTA] :2(…) radix syntax no longer suggests using .base (:2(42))

On Sat, 14 Oct 2017 00:54:02 -0700, alex.jakime...@gmail.com wrote: > Code: > say :2(1); > > > ¦«2015.12»: > This call only converts base-2 strings to numbers; value 1 is of type > Int, so cannot be converted! > (If you really wanted to convert 1 to a base-2 string, use 1.base(2) > instead.) >

Re: Perl6 on USB key?

Not really, unless you're just adding the binary and libraries to the stick and calling it from there instead of /usr/bin. If you want something that can run on it's own, I'd recommend using a Raspberry Pi Zero and 'converting' that to a USB stick. You'll have full linux-y goodness and be able

[perl #132012] [ANNOYING] Numeric values of signals are wrong (say +SIGUSR1)

On Fri, 13 Oct 2017 23:34:51 -0700, alex.jakime...@gmail.com wrote: > There's something regression-ish about it. > > Code: > say $*KERNEL.signal: SIGUSR1 > > ¦79b8ab9d3f^: > > 10 > > ¦79b8ab9d3f: > 30 > > > See (2017-06-02) >

[perl #132012] [ANNOYING] Numeric values of signals are wrong (say +SIGUSR1)

On Fri, 13 Oct 2017 23:34:51 -0700, alex.jakime...@gmail.com wrote: > There's something regression-ish about it. > > Code: > say $*KERNEL.signal: SIGUSR1 > > ¦79b8ab9d3f^: > > 10 > > ¦79b8ab9d3f: > 30 > > > See (2017-06-02) >

[perl #132293] [REGRESSION] It is no longer possible to create native ints with .new (int32.new(42))

On Sat, 14 Oct 2017 03:07:16 -0700, c...@zoffix.com wrote: > On Fri, 13 Oct 2017 23:08:20 -0700, alex.jakime...@gmail.com wrote: > > Code: > > say int32.new(42) > > > > > > ¦«2016.10,2016.11,2016.12,2017.01,2017.02,2017.03,2017.04.3,2017.05, > > 2017.06,2017.07,2017.08,2017.09»: > > 42 > > > > >

[perl #132293] [REGRESSION] It is no longer possible to create native ints with .new (int32.new(42))

On Sat, 14 Oct 2017 03:07:16 -0700, c...@zoffix.com wrote: > On Fri, 13 Oct 2017 23:08:20 -0700, alex.jakime...@gmail.com wrote: > > Code: > > say int32.new(42) > > > > > > ¦«2016.10,2016.11,2016.12,2017.01,2017.02,2017.03,2017.04.3,2017.05, > > 2017.06,2017.07,2017.08,2017.09»: > > 42 > > > > >

[perl #132300] [SEGV] say nqp::getlexdyn('')

# New Ticket Created by Zoffix Znet # Please include the string: [perl #132300] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132300 > m: use nqp; say nqp::getlexdyn('') rakudo-moar 0d217357a: OUTPUT: «(signal SEGV)»

[perl #132293] [REGRESSION] It is no longer possible to create native ints with .new (int32.new(42))

On Fri, 13 Oct 2017 23:08:20 -0700, alex.jakime...@gmail.com wrote: > Code: > say int32.new(42) > > > ¦«2016.10,2016.11,2016.12,2017.01,2017.02,2017.03,2017.04.3,2017.05, > 2017.06,2017.07,2017.08,2017.09»: > 42 > > > ¦«HEAD(012c80f)»: > No such method 'BUILDALLPLAN' for invocant of type >

[perl #132293] [REGRESSION] It is no longer possible to create native ints with .new (int32.new(42))

On Fri, 13 Oct 2017 23:08:20 -0700, alex.jakime...@gmail.com wrote: > Code: > say int32.new(42) > > > ¦«2016.10,2016.11,2016.12,2017.01,2017.02,2017.03,2017.04.3,2017.05, > 2017.06,2017.07,2017.08,2017.09»: > 42 > > > ¦«HEAD(012c80f)»: > No such method 'BUILDALLPLAN' for invocant of type >

Perl6 on USB key?

Hello, is there a way to run Perl6 and it’s libraries from a USB key? Best regards, Philippe

[perl #132295] [REGRESSION][LTA] :2(…) radix syntax no longer suggests using .base (:2(42))

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132295] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132295 > Code: say :2(1); ¦«2015.12»: This call only converts base-2

[perl #132294] [REGRESSION][PERF] INTERPOLATE-related change made matching of large strings slower

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132294] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132294 > Code: my $a = rx/aab/; 'a' x 99 ~ 'b' ~~ /$a/; say now -

[perl #131966] [REGRESSION][9999] Shaped native arrays with negative sizes (my int @a[-9999999999999999])

Actually, it is a regression. Code: my int @x[-2**63]; say @x.shape ¦«2015.12»: (-9223372036854775808) ¦«2016.06»: Illegal dimension in shape: -9223372036854775808. All dimensions must be integers bigger than 0 in block at /home/bisectable/git/whateverable/data/regressionable/15074816/snippet

[perl #132012] [ANNOYING] Numeric values of signals are wrong (say +SIGUSR1)

There's something regression-ish about it. Code: say $*KERNEL.signal: SIGUSR1 ¦79b8ab9d3f^: 10 ¦79b8ab9d3f: 30 See (2017-06-02) https://github.com/rakudo/rakudo/commit/79b8ab9d3f9a5499e8a7859f34b4499fb352ac13 On 2017-09-01 15:39:42, alex.jakime...@gmail.com wrote: > We now have a note in

[perl #132293] [REGRESSION] It is no longer possible to create native ints with .new (int32.new(42))

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132293] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132293 > Code: say int32.new(42)