eugene@eos.arc.nasa.gov (Eugene Miya) (11/09/90)
I suggest that we start the logical FAQ posting:
sources
general topics
I can collect some information like source, but because these are US Government
machines and subject to lots of bureaucracy, I suspect keeping interesting
results is touchy.
When we have enough info, I set a frequency of 1 month.
--e.n. miya, NASA Ames Research Center, eugene@eos.arc.nasa.gov
{uunet,mailrus,most gateways}!ames!eugene
AMERICA: CHANGE IT OR LOSE IT.
P.S. I will be at the SPEC meeting next week.eugene@eos.arc.nasa.gov (Eugene Miya) (11/09/90)
The other day while bicycling home with Doug Pase, I told him a cute
little analogy from the old line:
Those who can, do.
Those who can't, teach.
For several months, I've thought
Those who build hardware, try.
Those who can't, benchmark. (mostly end users)
I'm obviously one of the latter bearers of bad news.
We have far too few of the former in this country. Steve Lundstrom
pointed out that only those with supercomputers are really concern with
cycle counting (generalized of course).
--e.n. miya, NASA Ames Research Center, eugene@eos.arc.nasa.gov
{uunet,mailrus,most gateways}!ames!eugene
AMERICA: CHANGE IT OR LOSE IT.jbuck@galileo.berkeley.edu (Joe Buck) (11/09/90)
In article <7575@eos.arc.nasa.gov>, eugene@eos.arc.nasa.gov (Eugene Miya) writes: |> We have far too few of the former in this country. Steve Lundstrom |> pointed out that only those with supercomputers are really concern with |> cycle counting (generalized of course). Not so, Eugene. Those of us who do real-time DSP (for example, I used to do low-bit-rate speech for a living) count every cycle and get very upset at pipeline bubbles; we also have tiny memories to work with in many cases so we count every word. If anyone wants to discuss this, take it to comp.arch or comp.dsp or something. -- Joe Buck jbuck@galileo.berkeley.edu {uunet,ucbvax}!galileo.berkeley.edu!jbuck