I was doing some extensive mathematics with FORTRAN and C for a couple of years. From my own experience I can tell that FORTRAN is sometimes really better than C but not for its speed (one can make C perform as fast as FORTRAN by using appropriate coding style) but rather because of very well optimized libraries like LAPACK (which can, however, be called from C code as well, either linking against LAPACK directly or using the LAPACKE interface for C), and because of great parallelization. On my opinion, FORTRAN is really awkward to work with, and its advantages are not good enough to cancel that drawback, so now I am using C+GSL to do calculations.

使用现代标准和编译器，不!

Some of the folks here have suggested that FORTRAN is faster because the compiler doesn't need to worry about aliasing (and hence can make more assumptions during optimisation). However, this has been dealt with in C since the C99 (I think) standard with the inclusion of the restrict keyword. Which basically tells the compiler, that within a give scope, the pointer is not aliased. Furthermore C enables proper pointer arithmetic, where things like aliasing can be very useful in terms of performance and resource allocation. Although I think more recent version of FORTRAN enable the use of "proper" pointers.

对于现代实现，C通用优于FORTRAN(尽管它也非常快)。

http://benchmarksgame.alioth.debian.org/u64q/fortran.html

编辑:

一个公平的批评似乎是，基准测试可能是有偏见的。这里是另一个来源(相对于C)，将结果放在更多的上下文中:

http://julialang.org/benchmarks/

你可以看到C在大多数情况下优于Fortran(再次看到下面的批评也适用于这里);正如其他人所指出的，基准测试是一门不精确的科学，很容易偏袒一种语言而不是其他语言。但它确实说明了Fortran和C语言有相似的性能。

一般来说，FORTRAN比C慢。C可以使用硬件级指针，允许程序员手动优化。FORTRAN(在大多数情况下)不能访问硬件内存寻址黑客。(VAX FORTRAN是另一回事。)我从70年代开始断断续续地使用FORTRAN。(真的)。

然而，从90年代开始，FORTRAN已经发展到包括特定的语言结构，可以优化成内在的并行算法，真正可以在多核处理器上运行。例如，自动矢量化允许多个处理器同时处理数据向量中的每个元素。16个处理器——16个元素向量——处理需要1/16的时间。

在C语言中，您必须管理自己的线程并为多处理仔细设计算法，然后使用一堆API调用来确保并行性正确发生。

在FORTRAN中，您只需要为多处理仔细设计算法。编译器和运行时可以为您处理其余的工作。

您可以阅读一些关于高性能Fortran的内容，但是您会发现许多死链接。你最好阅读并行编程(比如OpenMP.org)以及FORTRAN如何支持并行编程。

我还没有听说过Fortan比C快得多，但是可以想象在某些情况下它会更快。关键不在于语言特征的存在，而在于那些(通常)不存在的特征。

一个例子是C指针。C指针几乎到处都在使用，但指针的问题是编译器通常无法判断它们是否指向同一个数组的不同部分。

例如，如果你写了一个strcpy例程，看起来像这样:

strcpy(char *d, const char* s)
{
  while(*d++ = *s++);
}

编译器必须在d和s可能是重叠数组的假设下工作。所以当数组重叠时，它不能执行会产生不同结果的优化。正如您所期望的，这在很大程度上限制了可以执行的优化类型。

[我应该注意到，C99有一个“restrict”关键字，显式地告诉编译器指针不重叠。还要注意，Fortran也有指针，语义不同于C语言，但指针不像C语言那样无处不在。

但是回到C与Fortran的问题上，可以想象，Fortran编译器能够执行一些对于(直接编写的)C程序可能无法实现的优化。所以我不会对这种说法感到太惊讶。不过，我确实希望性能差异不会太大。(~ 5 - 10%)

I think the key point in favor of Fortran is that it is a language slightly more suited for expressing vector- and array-based math. The pointer analysis issue pointed out above is real in practice, since portable code cannot really assume that you can tell a compiler something. There is ALWAYS an advantage to expression computaitons in a manner closer to how the domain looks. C does not really have arrays at all, if you look closely, just something that kind of behaves like it. Fortran has real arrawys. Which makes it easier to compile for certain types of algorithms especially for parallel machines.

在运行时系统和调用约定等方面，C语言和现代的Fortran非常相似，很难看出有什么不同。注意，这里的C实际上是基础C: c++是一个完全不同的问题，具有非常不同的性能特征。

这两种语言具有相似的特性集。性能上的差异来自Fortran不允许混淆的事实，除非使用了EQUIVALENCE语句。任何有别名的代码都不是有效的Fortran，但是它是由程序员而不是编译器来检测这些错误的。因此，Fortran编译器忽略了可能的内存指针别名，并允许它们生成更有效的代码。看一下C语言中的这个小例子:

void transform (float *output, float const * input, float const * matrix, int *n)
{
    int i;
    for (i=0; i<*n; i++)
    {
        float x = input[i*2+0];
        float y = input[i*2+1];
        output[i*2+0] = matrix[0] * x + matrix[1] * y;
        output[i*2+1] = matrix[2] * x + matrix[3] * y;
    }
}

这个函数在优化后会比Fortran函数运行得慢。为什么如此?如果你在输出数组中写入值，你可能会改变矩阵的值。毕竟，指针可以重叠并指向相同的内存块(包括int指针!)C编译器被迫从内存中重新加载所有计算的四个矩阵值。

在Fortran中，编译器只加载一次矩阵值，并将它们存储在寄存器中。它可以这样做是因为Fortran编译器假定指针/数组在内存中不重叠。

Fortunately, the restrict keyword and strict-aliasing have been introduced to the C99 standard to address this problem. It's well supported in most C++ compilers these days as well. The keyword allows you to give the compiler a hint that the programmer promises that a pointer does not alias with any other pointer. The strict-aliasing means that the programmer promises that pointers of different type will never overlap, for example a double* will not overlap with an int* (with the specific exception that char* and void* can overlap with anything).

If you use them you will get the same speed from C and Fortran. However, the ability to use the restrict keyword only with performance critical functions means that C (and C++) programs are much safer and easier to write. For example, consider the invalid Fortran code: CALL TRANSFORM(A(1, 30), A(2, 31), A(3, 32), 30), which most Fortran compilers will happily compile without any warning but introduces a bug that only shows up on some compilers, on some hardware and with some optimization options.