Re: Why C is much slower than Fortran

"H.W. Stockman" <hwstock@wizard.com>
2 Jun 1999 01:33:10 -0400

          From comp.compilers

Related articles
[3 earlier articles]
Re: Why C is much slower than Fortran harley@corton.inria.fr (Robert Harley) (1999-05-03)
Re: Why C is much slower than Fortran hrubin@stat.purdue.edu (1999-05-09)
Re: Why C is much slower than Fortran terryg@uswest.net (1999-05-16)
Re: Why C is much slower than Fortran gneuner@dyn.com (1999-05-16)
Re: Why C is much slower than Fortran reid@micro.ti.com (Reid Tatge) (1999-05-20)
Re: Why C is much slower than Fortran jhallen@world.std.com (1999-05-29)
Re: Why C is much slower than Fortran hwstock@wizard.com (H.W. Stockman) (1999-06-02)
Re: Why C is much slower than Fortran erik@arbat.com (Erik Corry) (1999-06-02)
Re: Why C is much slower than Fortran lindahl@pbm.com (1999-06-02)
Re: Why C is much slower than Fortran sokal@holyrood.ed.ac.uk (Daniel Barker) (1999-06-02)
Re: Why C is much slower than Fortran djb@koobera.math.uic.edu (1999-06-02)
Re: Why C is much slower than Fortran Peter.Mayne@compaq.com (Peter Mayne) (1999-06-03)
Re: Why C is much slower than Fortran lindahl@pbm.com (1999-06-06)
[3 later articles]
| List of all articles for this month |

From: "H.W. Stockman" <hwstock@wizard.com>
Newsgroups: comp.lang.c++,comp.compilers,comp.arch
Date: 2 Jun 1999 01:33:10 -0400
Organization: Compilers Central
References: <3710584B.1C0F05F5@hotmail.com> 99-05-011 99-05-037 99-05-057 99-05-142
Keywords: design, architecture

Joseph H Allen <jhallen@world.std.com> wrote
> We've been going over this argument for eons, with only two solutions
> provided:
>
> Fortran - generate fast, but possibly buggy code
> C, C++ - generate correct, but slow code
>
> The only true solution for the alias problem is going to come from hardware:


Two simpler solutions, that don't work for all cases, but for a surprisingly
large number:


(1) use the restrict keyword, from the upcoming ansi C standard;
(2) upon entry to functions with ambiguous passed pointer references,
    derefrence and copy heavily used data to locals.


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.