From: Jason Merrill <jason@redhat.com>
To: "Arsen Arsenović" <arsen@aarsen.me>,
"Jonathan Wakely" <jwakely.gcc@gmail.com>,
gcc-patches@gcc.gnu.org
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Marek Polacek <polacek@redhat.com>
Subject: Re: Handling of main() function for freestanding
Date: Fri, 14 Oct 2022 11:17:06 -0400 [thread overview]
Message-ID: <63ab1032-6ab6-7f77-2f78-7c48370b4bf7@redhat.com> (raw)
In-Reply-To: <1860348.8SKhNGa0Zi@bstg>
On 10/14/22 06:04, Arsen Arsenović wrote:
> On Thursday, 13 October 2022 23:16:02 CEST Jason Merrill wrote:
>> I liked in the previous version that you checked the return type of
>> main when !flag_hosted, here and in c_missing_noreturn_ok_p. Let's
>> bring that back.
> Ah, right; I forgot about that. What do you think of this?
Looks good to me, but a C maintainer should also approve it.
Jason
next prev parent reply other threads:[~2022-10-14 15:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 20:15 Jonathan Wakely
2022-09-29 6:00 ` Richard Biener
2022-09-29 7:12 ` Jakub Jelinek
2022-09-29 9:21 ` Jonathan Wakely
2022-10-04 22:25 ` Jason Merrill
2022-10-04 23:28 ` Joel Sherrill
2022-10-07 11:30 ` Jonathan Wakely
2022-10-07 13:51 ` Jason Merrill
2022-10-07 13:53 ` Jakub Jelinek
2022-10-13 17:03 ` Arsen Arsenović
2022-10-13 17:10 ` Jakub Jelinek
2022-10-13 17:26 ` Arsen Arsenović
2022-10-13 17:24 ` Jason Merrill
2022-10-13 20:14 ` Arsen Arsenović
2022-10-13 21:16 ` Jason Merrill
2022-10-14 10:04 ` Arsen Arsenović
2022-10-14 15:17 ` Jason Merrill [this message]
2022-10-21 10:33 ` Ping (c,c++): " Arsen Arsenović
2022-10-21 21:02 ` Joseph Myers
2022-10-23 11:54 ` Arsen Arsenović
2022-10-24 13:46 ` Jason Merrill
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=63ab1032-6ab6-7f77-2f78-7c48370b4bf7@redhat.com \
--to=jason@redhat.com \
--cc=arsen@aarsen.me \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=jwakely.gcc@gmail.com \
--cc=polacek@redhat.com \
/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).