* Byterun question
@ 1998-06-16 14:39 Michael Sperber [Mr. Preprocessor]
1998-06-22 8:29 ` Xavier Leroy
0 siblings, 1 reply; 2+ messages in thread
From: Michael Sperber [Mr. Preprocessor] @ 1998-06-16 14:39 UTC (permalink / raw)
To: caml-list
Hi,
I'm doing some hacking on the bytecode engine, and there's a bit of
code I don't unterstand:
byterun/fix_code.c refers to STOP as the instructions with the highest
opcode all over the place. Yet, byterun/instruct.h list EVENT and
BREAK after STOP. Could someone illuminate?
(BTW: Hacking the O'Caml implementation is really a pleasure,
especially compared with other ML implementations I'd rather
leave unnamed ... Thanks, guys!)
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Byterun question
1998-06-16 14:39 Byterun question Michael Sperber [Mr. Preprocessor]
@ 1998-06-22 8:29 ` Xavier Leroy
0 siblings, 0 replies; 2+ messages in thread
From: Xavier Leroy @ 1998-06-22 8:29 UTC (permalink / raw)
To: Michael Sperber [Mr. Preprocessor], caml-list
> byterun/fix_code.c refers to STOP as the instructions with the highest
> opcode all over the place. Yet, byterun/instruct.h list EVENT and
> BREAK after STOP. Could someone illuminate?
My pleasure. The EVENT and BREAK opcodes never occur in a bytecode
executable file. They are inserted by the debugger by run-time
modification of the bytecode. Hence, the program loading code in
byterun/fix_code.c always sees opcodes that are <= STOP.
- Xavier Leroy
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1998-06-22 23:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-06-16 14:39 Byterun question Michael Sperber [Mr. Preprocessor]
1998-06-22 8:29 ` Xavier Leroy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox