From: Joseph Myers <joseph@codesourcery.com>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Ping (c,c++): Handling of main() function for freestanding
Date: Fri, 21 Oct 2022 21:02:02 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2210212101520.150427@digraph.polyomino.org.uk> (raw)
In-Reply-To: <6289278.W5v1pFC7tW@bstg>
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
On Fri, 21 Oct 2022, Arsen Arsenović via Gcc wrote:
> Ping on this patch.
>
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603574.html
>
> For context, see the rest of this thread. TL;DR is that `int main'
> should implicitly return 0 on freestanding, without the other burdens of
> main (hosted should remain unchanged, as well as non-int `main's). This
> applies to both the C and C++ frontends.
I have no objections to the C changes.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-10-21 21:02 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
2022-10-21 10:33 ` Ping (c,c++): " Arsen Arsenović
2022-10-21 21:02 ` Joseph Myers [this message]
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=alpine.DEB.2.22.394.2210212101520.150427@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=arsen@aarsen.me \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@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).