Prev: weird g77 and gfortran
Next: Standard input
From: Bil Kleb on 6 May 2008 13:38
Hi,

This request just went out to our team:

itemize what we would want out of a compiler-writer visit

I can only think of two related questions:

What areas of the F95 cause the most pain w.r.t. optimization?

What can we do as code developers to "help" the compiler?

Other ideas?

Thanks,
--
Bil Kleb
http://fun3d.larc.nasa.gov
From: John Harper on 6 May 2008 17:52
In article <fvq52g$6j4$1(a)aioe.org>, Bil Kleb <Bil.Kleb(a)NASA.gov> wrote:
>Hi,
>
>This request just went out to our team:
>
> itemize what we would want out of a compiler-writer visit
>
>I can only think of two related questions:
....
>Other ideas?

What areas of the F2003 standard are causing you the most pain to
implement?

When do you think you'll be able to release a full f2003 compiler?

What areas of the F2008 standard do you think will cause you the most
pain to implement?

When do you think you'll be able to release a full f2008 compiler?

-- John Harper, School of Mathematics, Statistics and Computer Science,
Victoria University, PO Box 600, Wellington 6140, New Zealand
e-mail john.harper(a)vuw.ac.nz phone (+64)(4)463 6780 fax (+64)(4)463 5045
From: Thomas Koenig on 7 May 2008 15:14
On 2008-05-06, Bil Kleb <Bil.Kleb(a)NASA.gov> wrote:

> What can we do as code developers to "help" the compiler?

If you think something is broken, submit bug reports through
the appropriate channels, with self-contained, preferably small
test cases. Indicate what you expected of the compiler, and what
happened instead.

If the compiler in question happens to be a "bazaar" - style
open-source project, you can also volunteer to fix bugs :-)
 | 
Pages: 1
Prev: weird g77 and gfortran
Next: Standard input