At 7:00 PM + 6/15/03, [EMAIL PROTECTED] (via RT) wrote:
In ./tools/dev/extract_file_descriptions.pl, regexps searching for
"Id:" get mangled by CVS checkout.
This patch modifies them to "I[d]:".
This patch is against the mangled file one would see at checkout,
rather than the unmangled CVS-int
At 8:25 PM +0200 6/19/03, Leopold Toetsch wrote:
The primary question is: Why do we save and restore what part of context.
Very good question:
*) System stack gets saved since we have important info on it.
(Exception handlers when they're done, along with other control
information)
*) User stack
Jonathan Sillito wrote:
-Original Message-
From: Melvin Smith [mailto:[EMAIL PROTECTED]
I tried this, and there was a distinct slowdown on accessing the regs
through the dereference.
However now the registers are no longer in the Parrot_Context struct, so it
may be worth revisiting this .
Dan Sugalski wrote:
Reusing these things should be considered OK, though they couldn't be
reused without being reinitialized after any sort of stack manipulation
on return, since COW will make pointers change.
Thinking some time about this (and looking at the last sub.t [1]), IMHO
best will be
> -Original Message-
> From: Melvin Smith [mailto:[EMAIL PROTECTED]
>
> I tried this, and there was a distinct slowdown on accessing the regs
> through the dereference. Dan and I debated this because I had the same
> idea, but after profiling I proved Dan right. I think it is best
> optimiz
Dan Sugalski wrote:
At 5:07 PM +0200 6/18/03, Leopold Toetsch wrote:
2) performance of CPS sucks
Are you sure? Tell us what you *really* think... :)
Exactly that, what I've outlined. But, when its ok, to generate the
Continuation outside of a possible loop, then its as fast as using the
contro
