http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59612
--- Comment #7 from janus at gcc dot gnu.org --- (In reply to janus from comment #2) > Does -fdump-fortran-optimized actually do anything? The reason why I did not get any output from it is of course that it is only in effect if -ffrontend-optimize is given in addition. Maybe it would be worth to mention this in the documentation, e.g. like this: Index: invoke.texi =================================================================== --- invoke.texi (revision 206237) +++ invoke.texi (working copy) @@ -991,8 +991,9 @@ @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. +Output the parse tree after front-end optimization (if enabled via +@option{-ffrontend-optimize}). Only really useful for debugging the GNU +Fortran compiler itself. @item -fdump-parse-tree @opindex @code{fdump-parse-tree}