public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rlerallut at free dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/40474]  New: gcc 4.3 no longer warns about missing newlines at end of files (regression from 4.2)
Date: Wed, 17 Jun 2009 11:40:00 -0000	[thread overview]
Message-ID: <bug-40474-17848@http.gcc.gnu.org/bugzilla/> (raw)

When compiling a C or C++ program with gcc 4.3 (and 4.4), there is no longer a
warning about "no newline at end of file".

I work with people that use gcc 4.2, which emits the warning, and we use
-Werror, so this is a major hindrance for us.

I'm attaching a trivial C program:

$ gcc-4.2 -o newline newline.c
newline.c:4:2: warning: no newline at end of file
$

$ gcc-4.3 -o newline newline.c
$

Versions (all from debian unstable):
gcc-4.2 --version
gcc-4.2 (GCC) 4.2.4 (Debian 4.2.4-6)
gcc-4.3 --version
gcc-4.3 (Debian 4.3.3-11) 4.3.3
gcc-4.4 --version
gcc-4.4 (Debian 4.4.0-6) 4.4.0


Regards,
Romain


-- 
           Summary: gcc 4.3 no longer warns about missing newlines at end of
                    files (regression from 4.2)
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rlerallut at free dot fr


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40474


             reply	other threads:[~2009-06-17 11:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 11:40 rlerallut at free dot fr [this message]
2009-06-17 11:41 ` [Bug c/40474] " rlerallut at free dot fr
2009-06-17 13:35 ` joseph at codesourcery dot com
2009-06-17 13:52 ` rlerallut at free dot fr
2009-06-17 13:59 ` joseph at codesourcery dot com
2009-06-17 14:15 ` rlerallut at free dot fr
2009-06-17 14:28 ` joseph at codesourcery dot com
2009-06-18 16:43 ` manu at gcc dot gnu dot org
2009-06-18 18:05 ` rlerallut at free dot fr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-40474-17848@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).