From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28964 invoked by alias); 29 Dec 2013 18:08:43 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 28908 invoked by uid 48); 29 Dec 2013 18:08:35 -0000 From: "janus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/59612] iso_fortran_env segfaults with -fdump-fortran-original Date: Sun, 29 Dec 2013 18:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: unknown X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: janus at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-12/txt/msg02366.txt.bz2 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}