This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/59612] iso_fortran_env segfaults with -fdump-fortran-original
- From: "janus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 28 Dec 2013 13:40:02 +0000
- Subject: [Bug fortran/59612] iso_fortran_env segfaults with -fdump-fortran-original
- Auto-submitted: auto-generated
- References: <bug-59612-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59612
--- Comment #2 from janus at gcc dot gnu.org ---
Note that there are two small errors in the related documentation:
Index: gcc/fortran/invoke.texi
===================================================================
--- gcc/fortran/invoke.texi (revision 206176)
+++ gcc/fortran/invoke.texi (working copy)
@@ -989,11 +989,12 @@ Output the internal parse tree after translating t
into internal representation. Only really useful for debugging the
GNU Fortran compiler itself.
-@item -fdump-optimized-tree
+@item -fdump-fortran-optimized
@opindex @code{fdump-fortran-optimized}
Output the parse tree after front-end optimization. Only really
useful for debugging the GNU Fortran compiler itself.
+@item -dump-parse-tree
@opindex @code{fdump-parse-tree}
Output the internal parse tree after translating the source program
into internal representation. Only really useful for debugging the
Does -fdump-fortran-optimized actually do anything?