This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [gomp merge] Stage 2: OpenMP for the Fortran front end (take 2)
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: jakub at redhat dot com
- Cc: Tobias dot Schlueter at Physik dot Uni-Muenchen dot DE, gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Tue, 7 Feb 2006 08:39:54 -0500 (EST)
- Subject: Re: [gomp merge] Stage 2: OpenMP for the Fortran front end (take 2)
>
> On Tue, Feb 07, 2006 at 02:17:09PM +0100, Tobias.Schlueter@Physik.Uni-Muenchen.DE wrote:
> > > Oops, guess you want to see the actual patch too ;)
> >
> > Do you also have documentation patches? It should certainly be amended to say
> > that gfortran supports OpenMP extensions.
>
> Like this?
>
> 2006-02-07 Jakub Jelinek <jakub@redhat.com>
>
> * invoke.texi: Document -fopenmp.
> * gfortran.texi: Document OpenMP.
I think it would be better if your changelog entry was like:
* gfortran.texi (Extensions): Document OpenMP.
so people know what section this is being added to.
> +gfortran attempts to be OpenMP 2.5 compatible when invoked with
> +the @code{-fopenmp} option. The OpenMP Fortran runtime library
> +routines are provided both in a form of Fortran 90 module named
> +@code{omp_lib} and in a form of a Fortran @code{include} file named
> +@code{omp_lib.h}. When @code{-fopenmp} option is not used,
> +both fixed form and free form OpenMP directives are handled as comments,
> +
What about a link to the openmp homepage, that seems like a good idea
since we are following their specifications?
Thanks,
Andrew Pinski