From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29554 invoked by alias); 5 May 2006 07:10:15 -0000 Received: (qmail 29540 invoked by uid 48); 5 May 2006 07:10:06 -0000 Date: Fri, 05 May 2006 07:10:00 -0000 Message-ID: <20060505071006.29539.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/27436] gfortran: Abort compiling if there are insufficient data descriptors in format after reversion In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "fxcoudert 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-05/txt/msg00482.txt.bz2 List-Id: ------- Comment #1 from fxcoudert at gcc dot gnu dot org 2006-05-05 07:10 ------- (In reply to comment #0) > Currently, gfortran only detects that the IO format descriptor contains > insufficient data at run time. It would be great (though of low priority) if > it would find them at compile time. Indeed. > write(*,'(abc)') n That one we could diagnose. > write(10,"(i7,(' abcd'))", err=10) n, n This one, however, is not expected to give a warning since an err= specifier is present. It's true we could optimize it away as a "goto 10", but I think that is low priority :) -- fxcoudert at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxcoudert at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2006-05-05 07:10:05 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27436