Bump MOAR_REVISION for OSR-related SEGV fix.
allow code block in ** quantifiers, / foo ** { $a := 42 } /

In NQP the block can either provide a single item, which would be
handled as foo**42, means that it must match exactly $item times.
If the block provides a list [$min, $max], then the first two elems
are used, like in foo**0..3.
Note that the behaviour in rakudo is different, since we have Range
objects there.
fix separator use with code block in quantifier
support code blocks as quantifiers on parrot too
cleanup dynquant on moarvm
align to the standard about label prefix in dynquant
support code blocks as quantifiers on jvm as well
Get Moar with extop changes, leak fixes.
Bump to latest MoarVM.
bump nqp's moar for new extop interface
bump moarvm for proper extop discovery and inlinable lexotics
Numerous performance improvements to QAST -> MAST.

Includes a MoarVM revision bump to get MAST::Node improvements.
Sprinkle native types in QAST op registration.

Means we need to do a load less boxing at startup, only to throw it
all away again.
Get regex compiler using more attrs, less dynamics

Improves performance a bit further, since attribute lookups can be
far cheaper (and will JIT better).
Avoid repeated $*REGALLOC lookups.

Especially helpful in list-constructing loops.
Allow other integer representations for ranges in ** quantifier
flush filehandles and do not close stdout

AST printing was broken on my machine, also pmurias++ found the bug where we
close stdout when this is either not wanted or sane.
Build alternation offset arrays statically.

Before, we built them each time we wanted to evaluate an alternation.
This cuts nearly 800,000 object allocations out during the compilation
of CORE.setting, which is a measurable improvement.
Cache the reversed string for <after ...>.

We spent around > 0.5% of CORE.setting compilation time reversing the
string each time we wanted to do <after ...>. Cache it once we've done
it. Means MVM_string_flip becomes too low to make the profile now.
RT #122437 fix sprintf regression

The " " and "+" flags weren't being taken into account for floating
point numbers.  Added checks for these flags and some tests.