Hello world,

the attached two-letter patch fixed the spelling of two options and
makes sure they appear in lang.opt.urls.  Doc patch committed
as obvious and simple as r16-8750 after regenerating and testing.

Best regards

        Thomas

Fix typos in opindex for fc-prototypes and fc-prototypes-external.

gcc/fortran/ChangeLog:

        * invoke.texi (fc-prototypes): Correct spelling for opindex.
        (fc-prototypes-external): Likewise.
        * lang.opt.urls: Regenerate.
diff --git a/gcc/fortran/invoke.texi b/gcc/fortran/invoke.texi
index 90836657af1..b3e74148a08 100644
--- a/gcc/fortran/invoke.texi
+++ b/gcc/fortran/invoke.texi
@@ -2238,7 +2238,7 @@ shared by @command{gfortran}, @command{gcc}, and other GNU compilers.
 
 @table @gcctabopt
 
-@opindex c-prototypes
+@opindex fc-prototypes
 @cindex Generating C prototypes from Fortran BIND(C) enteties
 @item -fc-prototypes
 This option generates C prototypes from @code{BIND(C)} variable
@@ -2261,7 +2261,7 @@ $ gfortran -fc-prototypes -fsyntax-only foo.f90 > foo.h
 where the C code intended for interoperating with the Fortran code
 then uses @code{#include "foo.h"}.
 
-@opindex c-prototypes-external
+@opindex fc-prototypes-external
 @cindex Generating C prototypes from external procedures
 @item -fc-prototypes-external
 This option generates C prototypes from external functions and
diff --git a/gcc/fortran/lang.opt.urls b/gcc/fortran/lang.opt.urls
index c3549feb024..d401ac826da 100644
--- a/gcc/fortran/lang.opt.urls
+++ b/gcc/fortran/lang.opt.urls
@@ -312,6 +312,12 @@ LangUrlSuffix_Fortran(gfortran/Code-Gen-Options.html#index-fcheck-array-temporar
 fcray-pointer
 LangUrlSuffix_Fortran(gfortran/Fortran-Dialect-Options.html#index-fcray-pointer)
 
+fc-prototypes
+LangUrlSuffix_Fortran(gfortran/Interoperability-Options.html#index-fc-prototypes)
+
+fc-prototypes-external
+LangUrlSuffix_Fortran(gfortran/Interoperability-Options.html#index-fc-prototypes-external)
+
 fd-lines-as-code
 LangUrlSuffix_Fortran(gfortran/Fortran-Dialect-Options.html#index-fd-lines-as-code)
 

Reply via email to