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

2017-10-14 Thread Zoffix Znet via RT
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

2017-10-14 Thread Zoffix Znet via RT
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

2017-10-13 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
I'll take a look a bit later. It feels like the commit you mentioned is the right one, which makes me think that we can reject this ticket, but at that pace the spectest will get to turtle speeds even though all our changes will be justified. Anyway, I'll bisect it first and then we'll have a