ftp.delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:1610 |
From: | wpetiot AT worldnet DOT fr (William Petiot) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: .byte 0x64 |
Date: | Wed, 28 Feb 96 20:27:00 PST |
Organization: | Magical Wonder Band |
Lines: | 13 |
Message-ID: | <4hcs8u$1l6@aldebaran.sct.fr> |
References: | <Pine DOT A32 DOT 3 DOT 91 DOT 960227141833 DOT 9397B-100000 AT genius DOT tisl DOT soft DOT net> |
NNTP-Posting-Host: | client115.sct.fr |
Mime-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
In article <Pine DOT A32 DOT 3 DOT 91 DOT 960227141833 DOT 9397B-100000 AT genius DOT tisl DOT soft DOT net>, sandy AT genius DOT tisl DOT soft DOT net says... > >Hi all, > >Could anyone help me out with the code in sys/farptr.h. >All the functions have a ".byte 0x64" before the move. Why >is this required ? 0x64 is the opcode for prefix segment mnemonic : "ES:" farptr uses ES segment register to access memory, Gnu AS doesn't know the prefix ES: so one must use .byte 0x64 to encode this.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |