Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!mailrus!cwjcc!hal!ncoast!allbery From: allbery@ncoast.UUCP (Brandon S. Allbery) Newsgroups: comp.sys.ibm.pc Subject: Re: 80x86 numbering (was: 80486) Message-ID: <13258@ncoast.UUCP> Date: 15 Dec 88 22:55:25 GMT References: <15374@iuvax.cs.indiana.edu> <45900175@uxe.cso.uiuc.edu> <10254@watdragon.waterloo.edu> <2618@rti.UUCP> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: comp.sys.ibm.pc Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 22 As quoted from <2618@rti.UUCP> by bcw@rti.UUCP (Bruce Wright): +--------------- | What do you do with the architecture after the 80386 - outside of speedups | like more on-chip cache and higher MHz? The architecture has pretty much | reached its limit ... look at '386 native mode: a complete revamping of | the instruction set! Seems to me that after '386 native mode there's no | good place to take the architecture, it's already pretty much maxed out. | So you either make it faster or you go to a new chip design. Why then is | there all this hype about a '486? It'll probably only be a fast '386 | (like the 80186 to an 8086). +--------------- From what I have heard (I don't know how reliable it is), the 80486 will come out in two versions: a native one and an 80486/32632 (!) hybrid... after which the iAPX86 line will be discontinued, folded into the iAPX32 line. So the question becomes, what follows the 32932? ++Brandon -- Brandon S. Allbery, comp.sources.misc moderator and one admin of ncoast PA UN*X uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu comp.sources.misc is moving off ncoast -- please do NOT send submissions direct Send comp.sources.misc submissions to comp-sources-misc@.