# New Ticket Created by jerry gay
# Please include the string: [perl #38472]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38472 >
well, i'm not certain my perl 6 syntax is correct (it's still a moving
target, and i'm sti
On Feb 8, 2006, at 22:28, Joshua Isom wrote:
but an option to disable compile time optimizations would help with
the testing the interpreter instead of the compiler
It's not an optimization and it can't be turned off, as there are no
such opcodes like 'pow_i_ic_ic'. And again - the evaluatio
But with jit enabled on x86/freebsd/openbsd, I was having problems with
some of the pow functions. The rt number is #38382. Because of the
compile time optimization, it made it trickier to work with because the
compile time was ok, but the jit runtime wasn't, and it took me a
little while to
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #38469]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38469 >
Something's wrong with it:
$ ./parrot -Oc ack.pir 3
Ack(3, 3) = 61
$ /parrot -Oc
I'm still having troubles, when thinking about namespace PMCs and
implementation thereof.
Especially the relationship of class namespaces and the store_global
opcode.
We have e.g. this PIR snippets:
.sub main :main
cl = newclass 'Foo' # a class isa/hasa namespace ?!
...
.end
"jerry gay" <[EMAIL PROTECTED]> wrote:
while debugging partcl, leo asked will for some source comments to
understand where the generated code came from. i thought it should be
possible to walk the chain from the code emitter, and print the
calling sub's filename and line number in PIR.
walking t
while debugging partcl, leo asked will for some source comments to
understand where the generated code came from. i thought it should be
possible to walk the chain from the code emitter, and print the
calling sub's filename and line number in PIR.
walking the call chain is possible using a ParrotI
Leopold Toetsch wrote:
ori r11, r31, 20# r31 is 0
add r3, r4, r11# a 2nd oris is needed for constants > 0x
Well that's actually a bad example as there exists addi and addis
instructions.
But have a look at src/jit/arm/jit_emit.h emit_load_constant() and
follow the functio
"Jonathan Worthington" <[EMAIL PROTECTED]> wrote:
Better names and/or solutions welcome.
Chip has blessed this feature with a name - ":unique_reg" - and I've just
checked in the same stuff as before, but with the accepted name in place of
:non_volatile.
Jonathan
Joshua Isom wrote:
I guess this is one place where being CISC really is better than being
RISC.
It really depends on the hardare you are running. E.g.
add I0, I1, 20
translates either to something like:
lea %ecx, 20(%edx) # not yet but in case ..
or
ori r11, r31, 20# r31 is 0
# New Ticket Created by jerry gay
# Please include the string: [perl #38468]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38468 >
copyright info in the parrot repository has not been maintained. this
should be remedied.
# New Ticket Created by Will Coleda
# Please include the string: [perl #38467]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38467 >
Right now the Parrot::Test module is explicitly doing a check for a /
dev/null and chan
This failure is actually a bus error. You can generate it with:'
../../parrot tcl.pbc -e 'proc a {} {global q;puts $q};a'
Here's the gdb backtrace:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x01b4
0x0106fc60 in Parrot_dec_p (
"Joshua Isom" <[EMAIL PROTECTED]> wrote:
I guess this is one place where being CISC really is better than being
RISC. But how much improvement with outputting to a pbc first? But a
couple notes, there's no --help-optimize like --help-debug, and as far as I
know, there's no way to disable optim
I guess this is one place where being CISC really is better than being
RISC. But how much improvement with outputting to a pbc first? But a
couple notes, there's no --help-optimize like --help-debug, and as far
as I know, there's no way to disable optimizations completely, e.g.
this pir
.su
Parrot runs the ackermann benchmark faster than C.
leo
Heureka - from the -Ofun department
Or - running the ackermann function (and possibly other recursive
functions) really fast.
$ time ./parrot -Oc -C ack.pir 11
Ack(3, 11) = 16381
real0m0.567s
user0m0.559s
sys 0m0.008s
$ time ./
16 matches
Mail list logo