From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id BAA16860 for caml-redistribution; Tue, 23 Jun 1998 01:41:11 +0200 (MET DST) Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id KAA10474 for ; Mon, 22 Jun 1998 10:29:43 +0200 (MET DST) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by concorde.inria.fr (8.8.7/8.8.7) with ESMTP id KAA02422; Mon, 22 Jun 1998 10:29:39 +0200 (MET DST) Received: (from xleroy@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id KAA20406; Mon, 22 Jun 1998 10:29:39 +0200 (MET DST) Message-ID: <19980622102939.40008@pauillac.inria.fr> Date: Mon, 22 Jun 1998 10:29:39 +0200 From: Xavier Leroy To: "Michael Sperber [Mr. Preprocessor]" , caml-list@inria.fr Subject: Re: Byterun question References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from Michael Sperber [Mr. Preprocessor] on Tue, Jun 16, 1998 at 04:39:42PM +0200 Sender: weis > 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