From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17542 invoked by alias); 17 Jun 2009 13:59:26 -0000 Received: (qmail 17452 invoked by alias); 17 Jun 2009 13:59:11 -0000 Date: Wed, 17 Jun 2009 13:59:00 -0000 Message-ID: <20090617135911.17451.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c/40474] gcc 4.3 no longer warns about missing newlines at end of files (regression from 4.2) In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "joseph at codesourcery dot com" 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: 2009-06/txt/msg01199.txt.bz2 ------- Comment #4 from joseph at codesourcery dot com 2009-06-17 13:59 ------- Subject: Re: gcc 4.3 no longer warns about missing newlines at end of files (regression from 4.2) On Wed, 17 Jun 2009, rlerallut at free dot fr wrote: > (In reply to comment #2) > > This is deliberate; see bug 14331. > > Err... What happened to following the standard ? > " > If a source file that is not empty > does not end in a new-line character, or ends in a new-line char- > acter immediately preceded by a backslash character, the behavior > is undefined. > " Behavior being undefined means no requirement for a diagnostic, and the phase 1 mapping can introduce this newline in any case. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40474