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] gcc 4.3 no longer warns about missing newlines at end of files (regression from 4.2) Date: Thu, 18 Jun 2009 18:05:00 -0000 [thread overview] Message-ID: <20090618180458.13070.qmail@sourceware.org> (raw) In-Reply-To: <bug-40474-17848@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from rlerallut at free dot fr 2009-06-18 18:04 ------- (In reply to comment #7) > The warning was removed on purpose per user request, so this is WONTFIX. Keeping an once of compatibility (or adding an option) between two minor versions would have been appreciated. Or a pragma, whatever. Not all of us have the luxury of a homogeneous development environment. > We are sorry about the inconvenience this causes to you. We humbly suggest you > consider using a more modern editor, for example emacs, which will introduce a > newline at the end of the file. So does vim [flamebait right back at you]. However many of my colleagues use visual c++ which does not have this feature (or not by default). > Otherwise, your colleagues could perhaps update > to the same version of GCC you are using. Developing with different versions of > GCC is likely to cause some discrepancies because of fixed/new bugs. Yes. Not to mention the various behavior in floating point optimizations. Most of our Linux-using developers use gcc 4.2 on Ubuntu's latest "long term support" release. But part of my job is to evaluate the compilers we have available (or will have in the future). I therefore routinely use gcc from 4.1 to 4.4 as well as intel's icc and visual c++. It's already hard enough being one of the few linux people in a windows shop, you're not making my task easier. Well, I guess you can't please everyone all the time. Wontfix it is. I'll patch my local copy. Regards, Romain -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40474
prev parent reply other threads:[~2009-06-18 18:05 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-17 11:40 [Bug c/40474] New: " rlerallut at free dot fr 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 [this message]
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=20090618180458.13070.qmail@sourceware.org \ --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: linkBe 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).