From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31467 invoked by alias); 5 May 2010 06:52:16 -0000 Received: (qmail 30606 invoked by uid 48); 5 May 2010 06:51:54 -0000 Date: Wed, 05 May 2010 06:52:00 -0000 Message-ID: <20100505065154.30605.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/40165] Excessive warnings for REAL DO loops In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dfranke at gcc dot gnu dot org" 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 X-SW-Source: 2010-05/txt/msg00398.txt.bz2 ------- Comment #8 from dfranke at gcc dot gnu dot org 2010-05-05 06:51 ------- (In reply to comment #7) > OTOH I can see where a program that has a lot of real do loops would be > irritating.[...] So I suggest we mark as an enhancement and when some one has > time, we could implement a consolidated error message. This could backfire. Consider applications that make extensive use of computed GOTOs, PAUSE or any of the other deleted features. Shall we introduce flags for selectively enable/disable any of them? That's what -std={legacy|gnu|f*} does. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40165