Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site ut-ngp.UTEXAS Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!qantel!dual!mordor!ut-sally!ut-ngp!kjm From: kjm@ut-ngp.UTEXAS (Ken Montgomery) Newsgroups: net.micro.68k Subject: Re: Re**n: Bus Error Effluvia Message-ID: <2439@ut-ngp.UTEXAS> Date: Mon, 30-Sep-85 18:42:30 EDT Article-I.D.: ut-ngp.2439 Posted: Mon Sep 30 18:42:30 1985 Date-Received: Fri, 4-Oct-85 05:52:16 EDT References: <2393@ut-ngp.UTEXAS> <467@mtxinu.UUCP> Distribution: net Organization: UTexas Computation Center, Austin, Texas Lines: 25 [] >>How does one get this NOP generated in the correct places for compiled code >>that has to be portable? The synchronizing effect is not useful unless one >>can manage to invoke it. Even if one solves this problem, the problem of >>detecting all of the places where it is needed remains. [me] > >How does one write in a high-level language the idea that a store >might fault, that the fault is acceptable, and knowledge of the >fault status is in r0? This sort of code *isn't* portable (which >may be an argument for not using it), and happens only in deliberate, >thereby known, places. [Ed Gould] This is a valid objection to my objection. (I will admit that my objection was not truly robust.) But there is one point to consider: operating systems have such unusual code sequences in places; I, at least, would prefer to be able to integrate them with a minimum of pain -- ergo my question. -- The above viewpoints are mine. They are unrelated to those of anyone else, including my cat and my employer. Ken Montgomery "Shredder-of-hapless-smurfs" ...!{ihnp4,allegra,seismo!ut-sally}!ut-ngp!kjm [Usenet, when working] kjm@ngp.UTEXAS.EDU [Internet, if the nameservers are up]