public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/96284] Outdated C features should be made errors with newer standards
Date: Tue, 28 Jul 2020 07:39:18 +0000	[thread overview]
Message-ID: <bug-96284-4-EEnKYrOUlf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96284-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96284

--- Comment #7 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to David Brown from comment #6)
> I'm not bothered about my own code - I have makefiles with the relevant
> options set in case I make mistakes.  My hope is for gcc to be able to have
> stricter warnings to reduce bugs in code written now and in the future.  But
> I understand that it's also important not to cause trouble for existing code
> and build systems.

The implicit function declaration warning does not seem to be quite enough, it
would help programmers to turn it into an error. But that's what also impacts
configure scripts.

  parent reply	other threads:[~2020-07-28  7:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 13:16 [Bug c/96284] New: " david at westcontrol dot com
2020-07-22 14:09 ` [Bug c/96284] " rguenth at gcc dot gnu.org
2020-07-22 14:51 ` redi at gcc dot gnu.org
2020-07-22 17:18 ` msebor at gcc dot gnu.org
2020-07-22 17:33 ` msebor at gcc dot gnu.org
2020-07-28  5:57 ` egallager at gcc dot gnu.org
2020-07-28  7:20 ` david at westcontrol dot com
2020-07-28  7:39 ` fw at gcc dot gnu.org [this message]
2021-12-15  7:01 ` egallager at gcc dot gnu.org
2023-12-01  7:12 ` cvs-commit at gcc dot gnu.org
2023-12-01  7:12 ` cvs-commit at gcc dot gnu.org
2023-12-01  7:12 ` cvs-commit at gcc dot gnu.org
2023-12-01  7:12 ` cvs-commit at gcc dot gnu.org
2023-12-01  7:12 ` cvs-commit at gcc dot gnu.org
2023-12-01  7:15 ` fw at gcc dot gnu.org
2023-12-01  7:15 ` fw at gcc dot gnu.org
2023-12-01  8:21 ` sjames at gcc dot gnu.org
2023-12-01  8:21 ` sjames at gcc dot gnu.org
2023-12-01  8:41 ` david at westcontrol dot com

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-96284-4-EEnKYrOUlf@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).