386/387 asm question

Thread View: comp.sys.ibm.pc.programmer

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Ray Berry Tue, 20 Feb 1990 18:56

#1316

Author: Ray Berry
Date: Tue, 20 Feb 1990 18:56

16 lines
1128 bytes

	I am interested in learning whether the 387 supports the extended
addressing features of the 386.  For instance, the sample instruction
	
	fld	dword ptr [esi][eax*4]

	assembles fine both in MASM and TASM.  But when executed, (yes, 
it seems to execute ok) the 387 does not load the correct data.  (pc, 
real mode).  If I 'mov' the data to a 386 register it shows up fine, so 
I know the address is properly formed.  And if I convert the address to 
the conventional [si][bx] form, all is fine also. Incidentally, I'm
using Borland TD to make these observations.  Does anyone know about 
this?  Thanks in advance for any help.
-- 
Ray Berry  kb7ht  uucp: ...ole!ray CIS: 73407,3152 /* "inquire within" */
Seattle Silicon Corp. 3075 112th Ave NE. Bellevue WA 98004 (206) 828-4422

Re: 386/387 asm question

#1382

Author: Ray Berry
Date: Wed, 21 Feb 1990 17:38

10 lines
1003 bytes

>	fld	dword ptr [esi][eax*4]

	Call off the hounds.  TASM gets the award for this one.  Although
the list files show that tasm and masm both emit the same code for this
instruction, the instruction fails when the tasm module is linked but
works fine when the masm-assembled module is linked.  The tasm vers I
have is the original 1.0, and not what is currently shipping (1.01?).
-- 
Ray Berry  kb7ht  uucp: ...ole!ray CIS: 73407,3152 /* "inquire within" */
Seattle Silicon Corp. 3075 112th Ave NE. Bellevue WA 98004 (206) 828-4422

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads