Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!ogicse!intelhf!ichips!omews1!colwell From: colwell@omews1.intel.com (Robert Colwell) Newsgroups: comp.sys.intel Subject: Re: Technical books on Intel's 80x86 line wanted Message-ID: <1991Jan22.205343.19819@omews63.intel.com> Date: 22 Jan 91 20:53:43 GMT References: <1991Jan19.193711.18738@clinet.fi> <1991Jan22.180548.7527@hoss.unl.edu> Sender: news@omews63.intel.com (News Account) Reply-To: colwell@mipon2.intel.com (Robert Colwell) Organization: Intel Corp., Hillsboro, Oregon Lines: 21 In article <1991Jan22.180548.7527@hoss.unl.edu> savel@hoss.unl.edu (Bharat P. Savel) writes: >In article veit@du9ds3.uni-duisburg.de (Holger Veit) writes: >>dix@clinet.fi (Risto Kaivola) writes: >> >>>more precise, I need information on the 'internal representation' of >>>the instruction set. >i had the same problem when i started my project; i guess that you are >asking for material which is under properitaryship of INTEL; no way you >can find out... I certainly don't speak for Intel here, but as a disinterested observer I point out that all the bit encodings you could want appear to be clearly spelled out in the standard Intel literature; c.f. "i486 Microprocessor Programmer's Reference Guide". Or look into the gcc code, which targets x86 machines rather successfully, and must therefore incorporate the proper bit encodings. Bob Colwell colwell@mipon2.intel.com 503-696-4550 Intel Corp. JF1-19 5200 NE Elam Young Parkway Hillsboro, Oregon 97124