From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20900 invoked by alias); 15 Nov 2006 06:06:08 -0000 Received: (qmail 20864 invoked by uid 48); 15 Nov 2006 06:05:59 -0000 Date: Wed, 15 Nov 2006 06:06:00 -0000 Message-ID: <20061115060559.20863.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/28122] Undocumented gfortran options In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "brooks at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-11/txt/msg01356.txt.bz2 List-Id: ------- Comment #3 from brooks at gcc dot gnu dot org 2006-11-15 06:05 ------- It turns out that we can't set -fpreprocessed to "Undocumented", as it is shared with other front ends. However, it is documented in the GCC manual in the preprocessor section, and thus falls outside the "options specific to GNU Fortran" purview of the command-line options section in the gfortran manual. As such, I see no need to add duplicate documentation to it in the gfortran manual; there are already plenty of other preprocessor options that the "gfortran" command supports that are not in the manual, and from a user perspective this one is no different. Meanwhile, I have also removed -no-backend and -fmodule-private, instead of documenting them. Thus, I'm resolving this as fixed. -- brooks at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28122