Article View: comp.sys.intel
Article #1568Re: Still LOADALL
From: David DiGiacomo
Date: Fri, 23 Jan 1987 00:40
Date: Fri, 23 Jan 1987 00:40
18 lines
1435 bytes
1435 bytes
In article <1016@intelca.UUCP> clif@intelca.UUCP (Clif Purkiser) writes:
> LOADALL causes compatibility problems.
>
>6. The LOADALL instruction causes an illegal opcode exception on the 386.
>Thus 286 software which uses a LOADALL instruction will not run on a 386 system
>unless, the software first tests to see which processor it is running on and
>then uses different code sequences for the 80286 or 80386. Fortunately, the
>packages which do use the LOADALL instruction are being modified to do this.
Instead of modifying the applications, it's simpler to have the 386
system's illegal opcode exception simulate the LOADALL instruction,
which should be easy because...
>7. Everything useful that LOADALL does can be done already on a 386 using
> documented instructions without having to reset the part.
--
David DiGiacomo {decvax, ihnp4, ucbvax}!sun!david david@sun.arpa
Sun Microsystems, Mt. View, CA (415) 691-7495
Technical Details
Message-ID:
<11931@sun.uucp>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!seismo!nbires!hao!ames!oliveb!sun!davidReferences:
<399@prairie.UUCP> <1016@intelca.UUCP>Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!nbires!hao!ames!oliveb!sun!david From: david@sun.uucp (David DiGiacomo) Newsgroups: comp.sys.intel Subject: Re: Still LOADALL Message-ID: <11931@sun.uucp> Date: Thu, 22-Jan-87 19:40:13 EST Article-I.D.: sun.11931 Posted: Thu Jan 22 19:40:13 1987 Date-Received: Fri, 23-Jan-87 07:00:18 EST References: <399@prairie.UUCP> <1016@intelca.UUCP> Organization: Sun Microsystems, Inc. Lines: 18