2009/1/21 Slava Pestov <[email protected]>:
> One other thing to try: declare any words which operate on your VM
> tuple 'inline', then supposing the exec word has effect ( vm insn --
> vm ), put hints on it:
>
> HINTS: exec vm instruction ;
I'm slightly confused between this and the documentation, which seems
to imply that the syntax should be
HINTS: exec { vm instruction } ;
Either version gives a speedup of a further 15% or so.
I think I'm now at the point where any further speedup will have to be
in the individual instruction words. (In particular, the word to test
a character is very frequently used, and fairly messy. I'll work on
that next.
Thanks again for all the suggestions.
Paul.
PS Yet again, I found out how much the optimizer helps - I tried
replacing the case combinator with an array of quotations, which I
indexed by the instruction. Unfortunately, I have to call the
quotation, and the stack effect of a call can't be inferred, disabling
the optimizer.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk
