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 13:33:19 +0000	[thread overview]
Message-ID: <bug-53232-4-Fgv6pF8qxa@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 #11 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
(In reply to Vincent Lefèvre from comment #8)
> (In reply to comment #6)
> > Er, if you want to find portability problems for people not using C99 then
> > don't use -std=c99. Then -Wreturn-type warns about main.
> 
> There are several reasons one may want to use -std=c99, e.g. to be able to
> use C99 features when available (via autoconf and/or preprocessor tests).

In any case, there does not seem to be a -std value to say that the program
must be valid for all C90, C99, C11 and C17 standards (and the future C23
standard). That's what portability is about.

  parent reply	other threads:[~2023-01-20 13:33 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 [this message]
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-Fgv6pF8qxa@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).