Dan Sugalski [EMAIL PROTECTED] wrote:
At 12:31 PM +0200 7/14/03, Leopold Toetsch wrote:
I have moved some interpreter variables (classname_hash,
compreg_hash, Argv, Env) into one (SArray) list:
interpreter-iglobals.
There access isn't time critical, so the extra indirection wont harm.
This is
Gregor N. Purdy [EMAIL PROTECTED] wrote:
#define DO_OP(PC,INTERP) \
(PC = ((INTERP-op_func_table)[*PC])(PC,INTERP))
The easiest way to intercept this flow with minimal cost is to
have the mechanism that wants to take over replace the interpreter's
op_func_table with a block of pointers
Robert Spier wrote:
Sorry for a slightly off-topic post, but will Larry's State of the Onion
be posted online soon?
Yes.
sorry to reiterate the argument, but will also a text transcript of
the talk be posted online? the slides are beautiful, but without a few
words of explanation they are
The following doesn't work:
.sub _main
newsub $P0, Sub, _foo
invokecc $P0
end
.end
.sub _foo
# ...
.end
Indeed, it can be done by using Caddr and Cset, but shouldn't sub
names be considered global labels, too?
Luke
The plan is to follow Gregors idea to swap op_func_table/op_addr array,
if events got enqueued.
The internal check_events__ will get filled into a second op_func_table
which will then take over.
There are still some questions:
- How does the actual event structure look like?
- Is this a
Given the following example:
% cat test.imc
.sub _MAIN
.local sub command_sub
newsub command_sub, .Sub, __cmd_puts
.end
.sub __cmd_puts
print whee\n
.end
%../../../parrot -o test.pbc test.imc
error:imcc:store_labels: inter_cs label '__cmd_puts' not found
make: *** [test.pbc] Error 1
I
Hurm. I tried switching the order of the .subs, which allows it to
compile, but then running it seems to print whee forever. This
doesn't seem right. I'd have expected this program to not actually
output anything - I just create the .Sub, not invoke it...
On Tuesday, Jul 15, 2003, at 00:54
Luke Palmer [EMAIL PROTECTED] wrote:
The following doesn't work:
[ snip ]
Indeed, it can be done by using Caddr and Cset, but shouldn't sub
names be considered global labels, too?
Of course. But newsub and the whole calling convention stuff isn't
finished yet. Meaning the newsub opcode
Monday 14 July 2003 05:56, Robert Spier wrote:
Sorry for a slightly off-topic post, but will Larry's State of
the Onion be posted online soon?
Yes.
http://dev.perl.org/perl6/talks/
-R
Really? I can't find anything about TPC7 in this page..
-angel
On Tuesday, Jul 15, 2003, at 06:36 America/New_York, Leopold Toetsch
wrote:
Will Coleda [EMAIL PROTECTED] wrote:
Given the following example:
% cat test.imc
.sub _MAIN
.local sub command_sub
newsub command_sub, .Sub, __cmd_puts
.end
.sub __cmd_puts
print whee\n
.end
%../../../parrot -o
On Tue, Jul 15, 2003 at 10:15:57AM +0200, Leopold Toetsch wrote:
How is the described scheme supposed to work with JIT generated code ?
--
Jason
Will Coleda [EMAIL PROTECTED] wrote:
But, why did it compile one way and not the other? And why would the
program with the subs switched print out whee indefinitely? I would
expect it to print whee once, then create a sub object, then die.
It did compile, because the label was known.
And:
$
Jason Gloudon [EMAIL PROTECTED] wrote:
On Tue, Jul 15, 2003 at 10:15:57AM +0200, Leopold Toetsch wrote:
How is the described scheme supposed to work with JIT generated code ?
JIT code would be intersparsed with (JITted) CHECK_EVENTS() opcodes.
They would get emitted e.g. at backward branches
# New Ticket Created by Will Coleda
# Please include the string: [perl #22998]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=22998
Supresses a perldoc warning on core_ops.pod
-- attachment 1
On Tue, 15 Jul 2003, Will Coleda wrote:
# New Ticket Created by Will Coleda
# Please include the string: [perl #22998]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=22998
Supresses a perldoc warning on
Attached is a test program, showing an implementations for multiple
timers. GNU/linux only, but implementing the platform interface (and the
sighandler/message queue) shouldn't be too hard.
I'm using milli seconds resolution, which seems IMHO reasonable. The
Kernel only has HZ (1s/100 on many
Perl 6 Summary for the week ending 20030713
Welcome once again to the Perl 6 Summary, in a week of major
developments and tantalizing hints.
Starting, as usual, with what's happening in perl6-internals
Targeting Parrot from GCC
Discussion in the thread entitled 'WxWindows
Really? I can't find anything about TPC7 in this page..
Sorry, had to take it down. It'll be back up in a few days.
On Tue, Jul 15, 2003 at 04:48:56PM +0200, Leopold Toetsch wrote:
Attached is a test program, showing an implementations for multiple
It didn't arrive. Did you attach it, or did its name end .t ?
Nicholas Clark
Nicholas Clark wrote:
On Tue, Jul 15, 2003 at 04:48:56PM +0200, Leopold Toetsch wrote:
Attached is a test program, showing an implementations for multiple
It didn't arrive. Did you attach it, or did its name end .t ?
No extension was .c. Attachment was there:
$ mailq
-Queue ID- --Size--
Hi Piers,
Before you're deluged...
What's Ponie? Ponie is 'Perl On New Internal Architecture'
Err, no, because then it would have been Ponia (presumably the singular
feminine). The project is definitely Ponie (the neuter plural).
And, for the record, the retro-acronym was actually: 'Perl on
Piers Cawley wrote:
Targeting Parrot from GCC
Discussion in the thread entitled 'WxWindows Support / Interfacing
Libraries' centred on writing a Parrot backend to GCC. (No, I have no
idea what that has to do with the thread subject.) Tupshin Harper, Leo
Tötsch and Benjamin Goldberg
# New Ticket Created by Simon Glover
# Please include the string: [perl #23006]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23006
At the moment, if you build Parrot with long doubles on Linux/x86, then
On Wednesday 16 July 2003 09:23 am, Tupshin Harper wrote:
At one point, Tupshin suggested emulating a 'more
traditional stack-oriented processor' and I don't think he was
joking...
Indeed, I wasn't, but I wish somebody would at least have the decency to
tell me how insane this is. ;-)
Simon Glover (via RT) wrote:
# New Ticket Created by Simon Glover
# Please include the string: [perl #23006]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=23006
At the moment, if you build Parrot with long
25 matches
Mail list logo