public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/53232] No warning for main() without a return statement with -std=c99
Date: Fri, 20 Jan 2023 15:10:47 +0000	[thread overview]
Message-ID: <bug-53232-4-lJIiewC8wd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53232-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
(In reply to Jakub Jelinek from comment #17)
> Yeah, but warnings with high false positivity rates at least shouldn't be in
> -Wall.

Well, there already is -Wunused, which is included in -Wall (such warnings may
typically be emitted due to #if and also in temporary code when debugging), and
-Wsign-compare in C++.

Anyway, there is a first issue: the warning is inexistent, even with -Wextra.
There is a second issue: the warning is not emitted with -Wreturn-type when
there is a call to main(). Solving these two issues alone would not yield a
high false positivity rate with -Wall. (That said, I think that developers
should be encouraged to have an explicit "return" for main(); in particular,
this is really easy to do and improves the code readability, specially knowing
the difference of behavior with other languages, such as shell scripts and
Perl.)

      parent reply	other threads:[~2023-01-20 15:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 12:56 [Bug c/53232] New: " vincent-gcc at vinc17 dot net
2012-05-04 13:44 ` [Bug c/53232] " manu at gcc dot gnu.org
2012-05-04 14:34 ` redi at gcc dot gnu.org
2012-05-04 15:29 ` manu at gcc dot gnu.org
2012-05-04 15:39 ` redi at gcc dot gnu.org
2012-05-04 15:44 ` vincent-gcc at vinc17 dot net
2012-05-04 16:09 ` redi at gcc dot gnu.org
2012-05-04 16:12 ` redi at gcc dot gnu.org
2012-05-04 19:58 ` vincent-gcc at vinc17 dot net
2021-08-28 19:07 ` pinskia at gcc dot gnu.org
2023-01-20  7:21 ` pinskia at gcc dot gnu.org
2023-01-20 13:33 ` vincent-gcc at vinc17 dot net
2023-01-20 13:47 ` redi at gcc dot gnu.org
2023-01-20 13:52 ` jakub at gcc dot gnu.org
2023-01-20 13:59 ` vincent-gcc at vinc17 dot net
2023-01-20 14:01 ` jakub at gcc dot gnu.org
2023-01-20 14:29 ` vincent-gcc at vinc17 dot net
2023-01-20 14:31 ` jakub at gcc dot gnu.org
2023-01-20 15:10 ` vincent-gcc at vinc17 dot net [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=bug-53232-4-lJIiewC8wd@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).