Xref: utzoo comp.sys.intel:1750 alt.lang.asm:69
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!seas.gwu.edu!timur
From: timur@seas.gwu.edu (The Time Traveler)
Newsgroups: comp.sys.intel,alt.lang.asm
Subject: Re: Need help in porting 8088/286 assembly code to 386.
Message-ID: <3355@sparko.gwu.edu>
Date: 22 Jun 91 19:31:24 GMT
References: <1991Jun21.161443.13880@kofax.uucp>
Followup-To: comp.sys.intel
Organization: The George Washington University, Washington, D.C.
Lines: 25

In article <1991Jun21.161443.13880@kofax.uucp> jdm@kofax.uucp (James D. Murray) writes:
>
>    I am looking for any books/magazine articles that could help me in
>realizing the changes that must be made to 8086/80286 assembly code
>to make it 80386-only.  I am porting some assembly code from DOS and
>Windows to SCO Unix on a 386 machine and I need to optimize it for
>386-only operation.
>

The God of optimized 80x86 assembly is Michael Abrash, and he has one book
out (Zen of Assembly) that is very useful.  There's a second volume coming.
He has articles on graphics programming in Programmer's Journal.  Basically,
he specializes in optimized assembly with a concentration in graphics.

80286 code would probably be an easy conversion - 8088 code wouldn't.  
Why not?  Because coding for 386 Unix means protected mode assembly,
and that's very different real mode.  Granted, the operating system takes
care of most of the stuff, but assembly programming always means you
have to do most of the work yourself.

----------------------------------------------------------- The Time Traveler
Let me take you far away                                    a.k.a. Timur Tabi
You'd like a holiday                             Internet: timur@seas.gwu.edu
Exchange the cold days for the sun              Bitnet:          HE891C@GWUVM
The good times ... and fun         -- Scorpions (awesome concert 5/10/91!)