public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <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, 04 May 2012 14:34:00 -0000 [thread overview]
Message-ID: <bug-53232-4-ds6E8vpFad@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53232-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53232
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-04 14:33:53 UTC ---
(In reply to comment #1)
> Neither -Wmain warns about this... I think it is a bug, at least in the case of
> -Wmain.
Why? -Wmain checks the type of main, not whether it has a redundant 'return 0;'
as the last statement.
next prev parent reply other threads:[~2012-05-04 14:34 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 [this message]
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
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-ds6E8vpFad@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).