[doc]: Fix -fopenmp documentation (was Re: [gomp merge] OpenMP for the C front end and runtime)

[Diego Novillo <dnovillo at redhat dot com>]

Eric Botcazou wrote:

> 	* doc/invoke.texi: Document -fopenmp.
> 
> It is inconsistently mentioned in the "Code Generation Options" and documented 
> in the "Options That Control Optimization" section.
> 
Thanks.  Fixed with the attached patch.  I also removed the stale
reference to -lgomp.

OK for mainline?

2006-02-10  Diego Novillo  <dnovillo@redhat.com>

	* doc/invoke.texi: Move -fopenmp description to "Options for
	Code Generation".
	Remove reference to -lgomp.

Index: invoke.texi
===================================================================
--- invoke.texi	(revision 110834)
+++ invoke.texi	(working copy)
@@ -4721,15 +4721,6 @@ instrumentation (and therefore faster ex
 some protection against outright memory corrupting writes, but allows
 erroneously read data to propagate within a program.
 
-@item -fopenmp
-@opindex fopenmp
-@cindex openmp parallel
-Enable handling of OpenMP directives @code{#pragma omp} in C/C++ and
-@code{!$omp} in Fortran.  When @option{-fopenmp} is specified, the
-compiler generates parallel code according to the OpenMP Application
-Program Interface v2.5.  To generate the final exectuable, the runtime
-library @code{libgomp} must be linked in using @option{-lgomp}.
-
 @item -fstrength-reduce
 @opindex fstrength-reduce
 Perform the optimizations of loop strength reduction and
@@ -13251,6 +13242,14 @@ operator delete must always be of defaul
 An overview of these techniques, their benefits and how to use them
 is at @w{@uref{http://gcc.gnu.org/wiki/Visibility}}.
 
+@item -fopenmp
+@opindex fopenmp
+@cindex openmp parallel
+Enable handling of OpenMP directives @code{#pragma omp} in C/C++ and
+@code{!$omp} in Fortran.  When @option{-fopenmp} is specified, the
+compiler generates parallel code according to the OpenMP Application
+Program Interface v2.5 @w{@uref{http://www.openmp.org/}}.
+
 @end table
 
 @c man end