Re: Byterun question

From: Xavier Leroy (Xavier.Leroy@inria.fr)
Date: Mon Jun 22 1998 - 10:29:39 MET DST


Date: Mon, 22 Jun 1998 10:29:39 +0200
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: "Michael Sperber [Mr. Preprocessor]" <sperber@informatik.uni-tuebingen.de>,
Subject: Re: Byterun question
In-Reply-To: <y9lwwahpg0h.fsf@brabantio.informatik.uni-tuebingen.de>; from Michael Sperber [Mr. Preprocessor] on Tue, Jun 16, 1998 at 04:39:42PM +0200

> 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



This archive was generated by hypermail 2b29 : Sun Jan 02 2000 - 11:58:14 MET