Xref: utzoo comp.lang.fortran:4273 comp.lang.c:34491
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!smurf!flatlin!bagsend!pilhuhn!hwr
From: hwr@pilhuhn.uucp (Heiko W.Rupp)
Newsgroups: comp.lang.fortran,comp.lang.c
Subject: Re: Fortran vs. C for numerical work (SUMMARY)
Message-ID: <184a59d8.ARN0ebd@pilhuhn.uucp>
Date: 30 Nov 90 16:37:28 GMT
References: <9458:Nov2721:51:5590@kramden.acf.nyu.edu> <2392:Nov2902:59:0590@kramden.acf.nyu.edu> <7339@lanl.gov>
Reply-To: hwr%pilhuhn@bagsend.ka.sub.org
Followup-To: comp.lang.fortran,comp.lang.c
Lines: 28

Organization: Not an Organization

In article <7339@lanl.gov>, Tony Warnock writes:

>
>
>      Model        Multiplication Time     Memory Latency
>
>      YMP          5  clock periods         18 clock periods
>      XMP          4  clock periods         14 clock periods
>      CRAY-1       6  clock periods         11 clock periods
>
>      Compaq       25 clock periods         4  clock periods
>      Zenith      120 clock periods        30  clock periods

These data also depend on clock speed !!!

But did someone see a self vectorizing compiler for C as there are many
for Fortran ?????

-Heiko


--
 O|O  Heiko W.Rupp             hwr%pilhuhn@bagsend.ka.sub.org
  |   Gerwigstr.5            | There is someone in my head, but it't not me
  U   FRG-7500 Karlsruhe 1   |                       - Pink Floyd
      Voice : + 49 721 693642| Do You know where Your towel is ???


Brought to you by Super Global Mega Corp .com