Article View: comp.arch
Article #11354Re: DEC Alpha AXP System INTEGER Performance
From: Michael Upton
Date: Fri, 20 Nov 1992 16:04
Date: Fri, 20 Nov 1992 16:04
24 lines
1562 bytes
1562 bytes
Re: Why no byte write on Alpha? Our group is working on GaAs microprocessor designs, and we have made many of the same decisions that DEC made on Alpha. There are two main reasons to avoid byte read and write. 1) Adds a mux on reads, As Mark F. from HP has said, this is no big deal in CMOS. but what about other technologies? We are constantly finding archetectural decisions that have been made based on 1.2 micron CMOS technology that make things very difficult for us in GaAs. DEC has said that the architecture is to last for XX (25?) years. Decisions made based on current technology often look out of place decades later, look at the VAX. Granted, this one instruction will not make or break an implementation, but DEC has done a very good job of designing a technology neutral architecture. 2)a read-modify-write is required on writes. To allow ECC protected writeback primary cache, a RMW is needed to update the ECC bits. Mike Upton Gallium Arsenide Processor Project University of Michigan
Technical Details
Message-ID:
<1992Nov20.160417.22524@zip.eecs.umich.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!pmafire!news.dell.com!swrinde!zaphod.mps.ohio-state.edu!caen!umeecs!quip.eecs.umich.edu!uptonReferences:
<1698@niktow.canisius.edu> <8840086@hpfcso.FC.HP.COM>Show Full Headers
Complete Article Headers
Newsgroups: comp.arch Path: arc1-ca.pugleaf.net!sparky!uunet!pmafire!news.dell.com!swrinde!zaphod.mps.ohio-state.edu!caen!umeecs!quip.eecs.umich.edu!upton From: upton@quip.eecs.umich.edu (Michael Upton) Subject: Re: DEC Alpha AXP System INTEGER Performance Message-ID: <1992Nov20.160417.22524@zip.eecs.umich.edu> Sender: news@zip.eecs.umich.edu (Mr. News) Organization: University of Michigan EECS Dept., Ann Arbor References: <1698@niktow.canisius.edu> <8840086@hpfcso.FC.HP.COM> Date: Fri, 20 Nov 1992 16:04:17 GMT Lines: 24