From: Joseph Myers <joseph@codesourcery.com>
To: DJ Delorie <dj@redhat.com>
Cc: Jim Wilson <jimw@sifive.com>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH] RISC-V: Fix elfutils testsuite unwind failures.
Date: Mon, 4 Feb 2019 23:46:31 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1902042344140.28073@digraph.polyomino.org.uk> (raw)
In-Reply-To: <xntvhjdt7l.fsf@greed.delorie.com>
On Mon, 4 Feb 2019, DJ Delorie wrote:
> Jim Wilson <jimw@sifive.com> writes:
> > By the way, the ISO C standard allows programs to fall through the
> > bottom of main. This is defined as exactly equivalent to returning 0.
>
> Hmm... that's new in gcc 5, so color me surprised. As that is glibc's
> minimum build version, I retract my comment.
It's a C99 feature that I implemented for GCC 3.0.
2000-07-27 Joseph S. Myers <jsm28@cam.ac.uk>
* c-decl.c (finish_function): Don't treat 'main' specially unless
flag_hosted. In C99 mode, return 0 from 'main' unless
DEFAULT_MAIN_RETURN is otherwise defined.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-02-04 23:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 23:48 [PATCH] RISC-V: Fix elfutils testsuite unwind failures Jim Wilson
2019-01-14 13:38 ` Florian Weimer
2019-01-14 17:29 ` Jim Wilson
2019-01-17 17:05 ` Mark Wielaard
2019-01-21 5:55 ` Jim Wilson
2019-01-22 13:28 ` Mark Wielaard
2019-01-23 6:58 ` Jim Wilson
2019-01-24 2:51 ` Palmer Dabbelt
2019-01-28 21:18 ` Jim Wilson
2019-01-28 22:44 ` DJ Delorie
2019-01-28 23:10 ` Jim Wilson
2019-02-04 22:37 ` DJ Delorie
2019-02-04 23:01 ` Jim Wilson
2019-02-04 23:33 ` DJ Delorie
2019-02-04 23:46 ` Joseph Myers [this message]
2019-02-04 23:57 ` DJ Delorie
2019-02-05 0:01 ` Joseph Myers
2019-02-12 20:08 ` ping^2 " Jim Wilson
2019-02-13 12:03 ` Andreas Schwab
2019-02-13 16:33 ` Andreas Schwab
2019-02-13 22:25 ` Palmer Dabbelt
2019-02-18 9:56 ` Andreas Schwab
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1902042344140.28073@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dj@redhat.com \
--cc=jimw@sifive.com \
--cc=libc-alpha@sourceware.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).