comp.arch
- AMBA bus (rev.2, 1999) test support architecture,
Fawnizu
- Intel x86 memory model question,
Joe Seigh
- History Of Hardware Perfomance Counters,
Vasanth Venkatachalam
- MMIX satisfies Popek and Goldberg virtualization requirements?,
andrewspencers
- Opteron's branch prediction,
Grumble
- Re: Xbox 360 guts ripped open and exposed,
Niels Jørgen Kruse
- look forward to going to jail,
franks_csa
- hi,
san
- Cell Documents,
Del Cecchi
- Jum-And-Link (Mips),
Paminu
- Not enough parallelism in programming,
Joe Seigh
- Re: Not enough parallelism in programming,
Torben Ægidius Mogensen
- Re: Not enough parallelism in programming,
Stephen Fuld
- Re: Not enough parallelism in programming,
Torben Ægidius Mogensen
- Re: Not enough parallelism in programming,
Greg Lindahl
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Stephen Fuld
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Sander Vesik
- Re: Not enough parallelism in programming,
Rupert Pigott
- Re: Not enough parallelism in programming,
Joe Seigh
- Re: Not enough parallelism in programming,
Rupert Pigott
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Alexander Terekhov
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Seongbae Park
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Rupert Pigott
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
JJ
- Re: Not enough parallelism in programming,
Dr. Adrian Wrigley
- Re: Not enough parallelism in programming,
Joe Seigh
- Re: Not enough parallelism in programming,
JJ
- Re: Not enough parallelism in programming,
Dr. Adrian Wrigley
- Re: Not enough parallelism in programming,
Stephen Fuld
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Stephen Fuld
- Re: Not enough parallelism in programming,
Dan Koren
- Re: Not enough parallelism in programming,
Kelly Hall
- Re: Not enough parallelism in programming,
JJ
- Re: Not enough parallelism in programming,
Anne & Lynn Wheeler
- Re: Not enough parallelism in programming,
Dan Koren
- Re: Not enough parallelism in programming,
rambam
- Re: Not enough parallelism in programming,
Stephen Fuld
- Re: Not enough parallelism in programming,
Andreas Kaiser
- Re: Not enough parallelism in programming,
Scott A Crosby
- Re: Not enough parallelism in programming,
David Gay
- Re: Not enough parallelism in programming,
Andy Freeman
- Re: Not enough parallelism in programming,
Joe Seigh
- Re: Not enough parallelism in programming,
Chris Colohan
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
David Gay
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
David Gay
- Re: Not enough parallelism in programming,
glen herrmannsfeldt
- Re: Not enough parallelism in programming,
Hank Oredson
- Re: Not enough parallelism in programming,
Stephen Fuld
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Stephen Fuld
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Stephen Fuld
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
David Gay
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Dan Koren
- Re: Not enough parallelism in programming,
David Gay
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
David Gay
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Jan Vorbrüggen
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Ken Hagan
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Bernd Paysan
- Re: Not enough parallelism in programming,
Scott A Crosby
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Klaus Fehrle
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Sander Vesik
- Re: Not enough parallelism in programming,
Scott A Crosby
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Scott A Crosby
- Re: Not enough parallelism in programming,
Torben Ægidius Mogensen
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Chris Colohan
- Re: Not enough parallelism in programming,
Andrew Reilly
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Andrew Reilly
- Re: Not enough parallelism in programming,
Robert Myers
- Re: Not enough parallelism in programming,
Nick Maclaren
- Re: Not enough parallelism in programming,
Scott A Crosby
- Re: Not enough parallelism in programming,
anonymous
- Re: Not enough parallelism in programming,
MitchAlsup
- Is E7520 chipset "compatible" w/incoming Paxville DP ?,
kus@xxxxxxxx
- Re: ultrasparc IIe question,
Joe Seigh
- Using xfig to draw circuits?,
Paminu
- PCI V2.3 compatibility,
Eli
- Program to Draw Circuits?,
Paminu
- Memory disambiguation on new Intel cpus,
Joe Seigh
- Good book on modern x86 architecture?,
Hugh Fisher
- How is the FSB frequency assigned?,
arun
- Re: Soc Design career question,
mag
- Re: Virtual memory and memory protection,
John Savard
- RCU+SMR hazard pointers w/o memory barriers,
Joe Seigh
- BIOS usage in OS,
Zdenek Sojka
- Re: Homemade device/IC/LCD/Buttons/Processors/Chips/Beeper possible/affordable ??,
Patricia Shanahan
- Non Power of 2 Cache Sizes,
Vikas Mishra
- Re: Non Power of 2 Cache Sizes,
Anton Ertl
- Re: Non Power of 2 Cache Sizes,
Terje Mathisen
- Re: Non Power of 2 Cache Sizes,
Nick Maclaren
- Re: Non Power of 2 Cache Sizes,
Torben Ægidius Mogensen
- Re: Non Power of 2 Cache Sizes,
Nick Maclaren
- Re: Non Power of 2 Cache Sizes,
Dan Koren
- Re: Non Power of 2 Cache Sizes,
Chris Colohan
- Re: Non Power of 2 Cache Sizes,
bob_jenkins
- Re: Non Power of 2 Cache Sizes,
Rich Walker
- Re: Non Power of 2 Cache Sizes,
Terje Mathisen
- Re: Non Power of 2 Cache Sizes,
Nick Maclaren
- Re: Non Power of 2 Cache Sizes,
Terje Mathisen
- Re: Non Power of 2 Cache Sizes,
Nick Maclaren
- Re: Non Power of 2 Cache Sizes,
David Kanter
- Re: Non Power of 2 Cache Sizes,
Nick Maclaren
- Re: Non Power of 2 Cache Sizes,
Terje Mathisen
- Re: Non Power of 2 Cache Sizes,
Sander Vesik
- Re: Non Power of 2 Cache Sizes,
Anton Ertl
- Re: Non Power of 2 Cache Sizes,
Nick Maclaren
- Re: Non Power of 2 Cache Sizes,
Eugene Miya
- Message not available
- Re: Non Power of 2 Cache Sizes,
John Savard
- Re: Non Power of 2 Cache Sizes,
Joe Pfeiffer
- Re: Non Power of 2 Cache Sizes,
Seongbae Park
- Compiler/Architecture course on modern hardware,
lroland@xxxxxxxxx
- Re: Compiler/Architecture course on modern hardware,
Del Cecchi
- Re: Compiler/Architecture course on modern hardware,
dooleys
- Re: Compiler/Architecture course on modern hardware,
John Savard
- Re: Compiler/Architecture course on modern hardware,
David Kanter
- Re: Compiler/Architecture course on modern hardware,
Torben Ægidius Mogensen
- Re: Compiler/Architecture course on modern hardware,
Nick Maclaren
- Re: Compiler/Architecture course on modern hardware,
John Savard
- Re: Compiler/Architecture course on modern hardware,
Nick Maclaren
- Re: Compiler/Architecture course on modern hardware,
John Savard
- Re: Compiler/Architecture course on modern hardware,
Stephen Fuld
- Re: Compiler/Architecture course on modern hardware,
Del Cecchi
- Re: Compiler/Architecture course on modern hardware,
Stephen Fuld
- Re: Compiler/Architecture course on modern hardware,
Peter \"Firefly\" Lund
- Computer architecture teaching,
David Kanter
- Re: Computer architecture teaching,
Torben Ægidius Mogensen
- Re: DRM, Intel, Sony, virtualization and backdoors,
Chris Barts
- Good System Architecture Sites?,
sharon@xxxxxxxxxxxxxxxxxxxxx
- Smalltalk Processor,
Tejaswi
- memory in verilog(its urgent plz help),
ravindra kalla
- SoC bus architecture (typical),
Fawnizu
- ISA-independent programming language,
mihai cartoaje
- Re: ISA-independent programming language,
Peter \"Firefly\" Lund
- Re: ISA-independent programming language,
mihai cartoaje
- Re: ISA-independent programming language,
Torben Ægidius Mogensen
- Re: ISA-independent programming language,
John Savard
- Re: ISA-independent programming language,
Hank Oredson
- Re: ISA-independent programming language,
Anton Ertl
- Re: ISA-independent programming language,
David W. Schroth
- Re: ISA-independent programming language,
Dan Koren
- Re: ISA-independent programming language,
Stephen Fuld
- Re: ISA-independent programming language,
John Savard
- Re: ISA-independent programming language,
Hank Oredson
- Re: ISA-independent programming language,
Andrew Reilly
- Re: ISA-independent programming language,
Hank Oredson
- Re: ISA-independent programming language,
Andrew Reilly
- Re: ISA-independent programming language,
Hank Oredson
- Re: ISA-independent programming language,
Anton Ertl
- Re: ISA-independent programming language,
Hank Oredson
- Re: ISA-independent programming language,
Del Cecchi
- Re: ISA-independent programming language,
Anton Ertl
- Re: ISA-independent programming language,
Andrew Reilly
- Re: ISA-independent programming language,
Seongbae Park
- Re: ISA-independent programming language,
Terje Mathisen
- Re: ISA-independent programming language,
Ken Hagan
- Re: ISA-independent programming language,
Hank Oredson
- Re: ISA-independent programming language,
Terje Mathisen
- Re: ISA-independent programming language,
Nick Maclaren
- Re: ISA-independent programming language,
wclodius
- Re: ISA-independent programming language,
Nick Maclaren
- Re: ISA-independent programming language,
Peter \"Firefly\" Lund
- Re: ISA-independent programming language,
Nick Maclaren
- Re: ISA-independent programming language,
Torben Ægidius Mogensen
- Re: ISA-independent programming language,
Nick Maclaren
- Re: ISA-independent programming language,
Torben Ægidius Mogensen
- Re: ISA-independent programming language,
Nick Maclaren
- Re: ISA-independent programming language,
wclodius
- Re: ISA-independent programming language,
Nick Maclaren
- Re: ISA-independent programming language,
Anne & Lynn Wheeler
- Re: ISA-independent programming language,
Nick Maclaren
- Re: ISA-independent programming language,
Anne & Lynn Wheeler
- Re: ISA-independent programming language,
Terje Mathisen
- Re: ISA-independent programming language,
Jan Vorbrüggen
- Re: ISA-independent programming language,
Peter \"Firefly\" Lund
- Re: ISA-independent programming language,
Anton Ertl
- Re: ISA-independent programming language,
mihai cartoaje
- Re: ISA-independent programming language,
Hank Oredson
- Re: ISA-independent programming language,
John Savard
- Re: ISA-independent programming language,
Hank Oredson
- Re: ISA-independent programming language,
David Gay
- Re: ISA-independent programming language,
Nick Maclaren
- Re: ISA-independent programming language,
David Gay
- Re: ISA-independent programming language,
Hank Oredson
- Re: ISA-independent programming language,
Jan Vorbrüggen
- Re: ISA-independent programming language,
John Savard
- Re: ISA-independent programming language,
Hank Oredson
- Re: ISA-independent programming language,
Michel Hack
- Re: ISA-independent programming language,
mihai cartoaje
- Re: ISA-independent programming language,
mihai cartoaje
- What was new&important in computer architecture 10 years ago ?,
kus@xxxxxxxx
- Re: What was new&important in computer architecture 10 years ago ?,
Nick Maclaren
- Re: What was new&important in computer architecture 10 years ago ?,
Del Cecchi
- Re: What was new&important in computer architecture 10 years ago ?,
Anne & Lynn Wheeler
- Re: What was new&important in computer architecture 10 years ago ?,
prep
- Re: What was new&important in computer architecture 10 years ago ?,
Del Cecchi
- Re: What was new&important in computer architecture 10 years ago ?,
Nick Maclaren
- Re: What was new&important in computer architecture 10 years ago ?,
Dan Koren
- Re: What was new&important in computer architecture 10 years ago ?,
George Coulouris
- Re: What was new&important in computer architecture 10 years ago ?,
Dan Koren
- Re: What was new&important in computer architecture 10 years ago ?,
Nick Maclaren
- Re: What was new&important in computer architecture 10 years ago ?,
Jeff Kenton
- Re: What was new&important in computer architecture 10 years ago ?,
Joe Pfeiffer
- Re: What was new&important in computer architecture 10 years ago ?,
John Mashey
- Re: What was new&important in computer architecture 10 years ago ?,
Dan Koren
- Re: What was new&important in computer architecture 10 years ago ?,
Jeff Kenton
- Re: What was new&important in computer architecture 10 years ago ?,
Dan Koren
- Re: What was new&important in computer architecture 10 years ago ?,
Anne & Lynn Wheeler
- Re: What was new&important in computer architecture 10 years ago ?,
Ketil Malde
- Re: What was new&important in computer architecture 10 years ago ?,
Anne & Lynn Wheeler
- Branch prediction using counters for sale !,
Skybuck Flying
- Re: wanting to create my own assembler,
randyhyde@xxxxxxxxxxxxx
- internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
MitchAlsup
- Re: internal call/ret stack,
Nick Maclaren
- Re: internal call/ret stack,
glen herrmannsfeldt
- Re: internal call/ret stack,
Alex McDonald
- Re: internal call/ret stack,
glen herrmannsfeldt
- Re: internal call/ret stack,
Terje Mathisen
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
Terje Mathisen
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
Torben Ægidius Mogensen
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
Nick Maclaren
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
Tom Linden
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
Dan Koren
- Re: internal call/ret stack,
Anton Ertl
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
Dan Koren
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
glen herrmannsfeldt
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
glen herrmannsfeldt
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
glen herrmannsfeldt
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
Dan Koren
- Re: internal call/ret stack,
Peter \"Firefly\" Lund
- Re: internal call/ret stack,
Seongbae Park
- Re: internal call/ret stack,
Maynard Handley
- Re: internal call/ret stack,
Seongbae Park
- Re: internal call/ret stack,
Anton Ertl
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- <Possible follow-ups>
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Andy Freeman
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Andy Freeman
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Andy Freeman
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Andy Freeman
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Andy Freeman
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
rafe
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Tim McCaffrey
Opteron hypertransport interface,
acthom
Message not available
circular buffer,
ravindra kalla
HPS influence on internal VAX discussions at DEC?,
Peter \"Firefly\" Lund
Re: CPU <> Memory chip communication interface,
Peter \"Firefly\" Lund
Re: Hardware Multithreading,
Walter Banks
Guantanamo Bay,
franks_csa
IBM's training.,
franks_csa
Russia & China better then India.,
franks_csa
Effeminates ask.,
franks_csa
SLT with Overflow Detection,
Paminu
RISC binary fragility (was Re: Code density and performance?),
Dysthymicdolt
Validy Technology: A program protection method that really works.,
jcc
Is the interleaved marker idea patentable ?,
Skybuck Flying
Idle Thread And Processor Stalls,
John Doe
ALU control lines?,
Paminu
bit notation in CPU?,
Paminu
Blade Servers -- are they cost effective?,
eventhelix
My first 1-bit FullAdder,
Paminu
Re: Cache coherency protocols: Write-update versus write-invalidate,
Petter Gustad
Set on less that operation??,
Paminu
Cache coherency info,
Neo
Re: Computer Registry Software-Microsoft I.E,
Stephen J Rush
computer architecture,
ravindra kalla
MPI Programmer Position Available,
Dhabaleswar Panda
The variable bit cpu,
Skybuck Flying
Re: OoO VAX (was: Code density and performance?),
Anton Ertl
Re: Cluster computing drawbacks,
Greg Lindahl
Re: Code density and performance?,
glen herrmannsfeldt
- <Possible follow-ups>
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Andrew Reilly
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Andrew Reilly
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Andrew Reilly
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Eric P.
- Re: Code density and performance?,
dooleys
- Re: Code density and performance?,
Eric P.
- Re: Code density and performance?,
Dennis M. O'Connor
- Re: Code density and performance?,
John Mashey
- Re: Code density and performance? [really Part 1 of 3: Micro economics 101],
John Mashey
- Re: Code density and performance? [really Part 1 of 3: Micro economics 101],
Nick Maclaren
- Re: Part 1 of 3: Micro economics 101 (was: Code density ...),
Anton Ertl
- Re: Part 1 of 3: Micro economics 101 (was: Code density ...),
Eric P.
- Re: Part 1 of 3: Micro economics 101 (was: Code density ...),
Tom Linden
- Re: Part 1 of 3: Micro economics 101 (was: Code density ...),
Andrew Reilly
- Re: Part 1 of 3: Micro economics 101 (was: Code density ...),
Tom Linden
- Re: Part 1 of 3: Micro economics 101 (was: Code density ...),
already5chosen
- Re: Part 1 of 3: Micro economics 101 (was: Code density ...),
John Mashey
- Re: Code density and performance? [really Part 1 of 3: Micro economics 101],
already5chosen
- Re: Code density and performance? [really Part 1 of 3: Micro economics 101],
Tom Linden
- Re: Code density and performance? [really Part 2b of 3: Micro economics 101],
John Mashey
- Re: Code density and performance? [really Part 2b of 3: Micro economics 101],
prep
- PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
John Mashey
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
John Savard
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
John Mashey
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Eric P.
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Eric P.
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Anne & Lynn Wheeler
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Sander Vesik
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
glen herrmannsfeldt
- Message not available
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Anton Ertl
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Jan Vorbrüggen
- Message not available
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
- Message not available
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
- Message not available
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
- Message not available
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
- Message not available
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Jan Vorbrüggen
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Jan Vorbrüggen
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
Message not availableRe: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Terje Mathisen
Message not availableRe: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Niels Jørgen Kruse
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Jan Vorbrüggen
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
already5chosen
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Terje Mathisen
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Terje Mathisen
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Anton Ertl
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Bill Todd
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Terje Mathisen
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Tom Linden
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
John Savard
Message not availableRe: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Eric P.
Message not availableRe: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Eric P.
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Tom Linden
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
John Mashey
Re: Part 1 of 3: Micro economics 101 (was: Code density ...),
Nick Maclaren
Message not available
Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Eric P.
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Eric P.
- Re: Code density and performance?,
Nick Maclaren
- Page table hierarchies,
David Kanter
- Re: Page table hierarchies,
Eric P.
- Re: Page table hierarchies,
Sander Vesik
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Eric Pattison
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Andrew Reilly
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Kees van Reeuwijk
- Re: Code density and performance?,
Nick Maclaren
- Re: Code density and performance?,
Anne & Lynn Wheeler
- Re: Code density and performance?,
Tom Linden
- Re: Code density and performance?,
Bernd Paysan
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Ketil Malde
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Ketil Malde
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Seongbae Park
- Re: Code density and performance?,
russell kym horsell
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Seongbae Park
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Jan Vorbrüggen
- Re: Code density and performance?,
Seongbae Park
- Re: Code density and performance?,
Anne & Lynn Wheeler
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Andrew Reilly
- Re: Code density and performance?,
Andrew Reilly
- Re: Code density and performance?,
Anton Ertl
- Re: Code density and performance?,
Bernd Paysan
- Re: Code density and performance?,
Anne & Lynn Wheeler
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
David Kanter
- Re: Code density and performance?,
Bill Todd
- Re: Code density and performance?,
Peter Grandi
- Re: Code density and performance?,
Bill Todd
- Message not available
- Re: Code density and performance?,
Bill Todd
- Re: Code density and performance?,
Peter Grandi
Re: Code density and performance?,
Peter Grandi
Re: Code density and performance?,
Bill Todd
Re: Code density and performance?,
Peter Grandi
Re: Code density and performance?,
Jan Vorbrüggen
Re: Code density and performance?,
Stephen Fuld
Message not availableRe: Code density and performance?,
Nick Maclaren
Message not availableRe: Code density and performance?,
Nick Maclaren
Message not availableRe: Code density and performance?,
Nick Maclaren
Message not availableRe: Code density and performance?,
Nick Maclaren
Message not availableRe: Code density and performance?,
Nick Maclaren
Re: Code density and performance?,
Anne & Lynn Wheeler
Re: Code density and performance?,
Peter Grandi
Re: Code density and performance?,
Andrew Reilly
Message not availableRe: Code density and performance?,
Stephen Fuld
Message not availableRe: Code density and performance?,
Peter Grandi
Message not availableRe: Code density and performance?,
Stephen Fuld
Message not availableRe: Code density and performance?,
Nick Maclaren
Re: Code density and performance?,
David Gay
Message not availableRe: Code density and performance?,
Del Cecchi
Message not availableRe: Code density and performance?,
Del Cecchi
Re: Code density and performance?,
Peter Grandi
Re: Code density and performance?,
Stephen Fuld
Re: Code density and performance?,
Stephen Fuld
Re: Code density and performance?,
Peter Grandi
Re: Code density and performance?,
Terje Mathisen
Re: Code density and performance?,
Peter Grandi
Re: Code density and performance?,
Linus Torvalds
Message not availableRe: Code density and performance?,
Peter Grandi
Message not availableRe: Code density and performance?,
Stephen Fuld
Re: Code density and performance?,
Bill Todd
Re: Code density and performance?,
Stephen Fuld
Re: Code density and performance?,
Terje Mathisen
Re: Code density and performance?,
Bill Todd
Re: Code density and performance?,
Terje Mathisen
Re: Code density and performance?,
Bill Todd
Re: Code density and performance?,
Terje Mathisen
Re: Code density and performance?,
Bill Todd
Re: Code density and performance?,
Terje Mathisen
Re: Code density and performance?,
Bill Todd
Re: Code density and performance?,
already5chosen
Re: Code density and performance?,
Terje Mathisen
Re: Code density and performance?,
already5chosen
Re: Code density and performance?,
already5chosen
Re: Code density and performance?,
Terje Mathisen
Re: Code density and performance?,
Peter Grandi
Re: Code density and performance?,
George Coulouris
Re: Code density and performance?,
Peter Grandi
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
- Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Peter \"Firefly\" Lund
- Silly new instructions,
Peter \"Firefly\" Lund
- Re: Silly new instructions,
John Savard
- Re: Silly new instructions,
Peter \"Firefly\" Lund
- Re: Silly new instructions,
John Savard
- Re: Silly new instructions,
John Ahlstrom
- Re: Silly new instructions,
Dan Koren
- Re: Silly new instructions,
Peter \"Firefly\" Lund
- Re: Silly new instructions,
Torben Ægidius Mogensen
- Re: Silly new instructions,
John Savard
- Re: Silly new instructions,
John Ahlstrom
- Re: Silly new instructions,
Dan Koren
- Re: Silly new instructions,
John R. Levine
- Re: Silly new instructions,
Dan Koren
- Re: Silly new instructions,
Tom Linden
- Re: Silly new instructions,
John Ahlstrom
- Re: Silly new instructions,
Joe Pfeiffer
- Re: Silly new instructions,
John Ahlstrom
- Re: Silly new instructions,
Joe Pfeiffer
- Re: Silly new instructions,
John Ahlstrom
Re: PART 3. Why it seems difficult to make an OOO VAX competitive (really long),
Nick Maclaren
Re: Code density and performance?,
Eric P.
Re: Code density and performance?,
David Gay
Re: Code density and performance?,
Nick Maclaren
Re: Code density and performance?,
Nick Maclaren
Re: Code density and performance?,
Nick Maclaren
Re: Itanium versus Others,
Del Cecchi
- Re: Itanium versus Others,
Robert Myers
- Re: Itanium versus Others,
John Savard
- <Possible follow-ups>
- Re: Itanium versus Others,
Maynard Handley
- Re: Itanium versus Others,
Tarjei T. Jensen
- Re: Itanium versus Others,
Tom Linden
- Re: Itanium versus Others,
John Savard
- Re: Itanium versus Others,
Rupert Pigott
- Re: Itanium versus Others,
John Savard
- Re: Itanium versus Others,
Dan Koren
- Re: Itanium versus Others,
Rupert Pigott
- Re: Itanium versus Others,
Casper H . S . Dik
- Re: Itanium versus Others,
Nick Maclaren
- Re: Itanium versus Others,
Jean-Marc Bourguet
- Re: Itanium versus Others,
Dan Koren
- Re: Itanium versus Others,
rambam
- Re: Itanium versus Others,
Del Cecchi
- Re: Itanium versus Others,
Dan Koren
- Message not available
- Re: Itanium versus Others,
Dan Koren
- Re: Itanium versus Others,
Bill Todd
- Re: Itanium versus Others,
Rupert Pigott
