Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mcnc!ece-csc!ncrcae!ncr-sd!hp-sdd!megatek!mana!hollen
From: hollen@mana.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: NOP
Message-ID: <187@megatek.UUCP>
Date: Thu, 1-Oct-87 12:25:10 EDT
Article-I.D.: megatek.187
Posted: Thu Oct  1 12:25:10 1987
Date-Received: Sat, 3-Oct-87 09:05:48 EDT
References: <2306@sphinx.uchicago.edu> <4478@amd.AMD.COM> <309@ncrcan.UUCP>
Sender: news@megatek.UUCP
Reply-To: hollen@mana.UUCP (Dion Hollenbeck)
Organization: Megatek Corporation, San Diego, Ca.
Lines: 22
Keywords: NOP

In article <309@ncrcan.UUCP> brian@ncrcan.UUCP () writes:
>In article <4478@amd.AMD.COM> ching@amd.UUCP (Mike Ching) writes:
>>.... The NOPs are never executed and don't slow down the
>>processor.
>>
>>mike ching
>
>Sorry, but the NOPS are always executed (how would the processor know that
>it is in fact a NOP, if it didn't execute it) and each execution takes 
>a finite, albeit minimal amount of execution time.


Sorry, Brian, but in almost all cases, the NOP's ARE NEVER EXECUTED.  This
is because the assembler places them just after a JMP instruction.  Since
the path of execution goes AROUND the NOP, it is not executed.  Reading the
several replies to the original question would have told you this.


	Dion Hollenbeck             (619) 455-5590 x2814
	Megatek Corporation, 9645 Scranton Road, San Diego, CA  92121
			{sdcsvax,hplabs}!hp-sdd!megatek!hollen
			{sdcsvax,seismo}!esosun!