Message-ID: <203@westcsr.UUCP>
Date: Thu, 3-Jan-85 08:59:09 EST
Article-I.D.: westcsr.203
Posted: Thu Jan  3 08:59:09 1985
Date-Received: Tue, 8-Jan-85 03:02:47 EST
Organization: CS Dept., Westfield College, London
Lines: 18
Xref: watmath net.micro.cpm:3307 net.micro:9011

<>
	I have a library in .IRL format that contains, amongst others,
one routine called IN and another called OUT. When linked with LINK-80
these are correctly read from the library and appear in the symbol table
but the instructions that CALL them have the wrong addresses.

	I assume that if I were to give them different names then everything
would be OK (other routines from the library link with no problems) and the
only thing about these two is that they have the same names as 8080 op-codes
but LINK doesn't know about those.

	Can anybody suggest what might be going on and provide a fix. I
don't want to change the names of the routines because I have a lot of
source code that refers to them.

Thanks,
Phil Thompson	..!ukc!west44!westcsr
		..!ukc!west44

Message-ID: <1288@orca.UUCP>
Date: Sun, 6-Jan-85 22:39:55 EST
Article-I.D.: orca.1288
Posted: Sun Jan  6 22:39:55 1985
Date-Received: Wed, 9-Jan-85 05:43:03 EST
References: <203@westcsr.UUCP>
Organization: Tektronix, Wilsonville OR
Lines: 15
Xref: watmath net.micro.cpm:3311 net.micro:9024

[]

	"I have a library in .IRL format that contains, amongst others,
	one routine called IN and another called OUT. When linked with
	LINK-80 these are correctly read from the library and appear in
	the symbol table but the instructions that CALL them have the
	wrong addresses ... Can anybody suggest what might be going on
	and provide a fix."

Look to the assembler instead of the linker.  Many assemblers will
quietly substitute the value of the opcode (such as IN or OUT) when you
use it as an address in an instruction.

  -- Andrew Klossner   (decvax!tektronix!orca!andrew)       [UUCP]
                       (orca!andrew.tektronix@csnet-relay)  [ARPA]