From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches@gcc.gnu.org, rdsandiford@googlemail.com
Subject: Re: C1X _Noreturn
Date: Wed, 24 Aug 2011 18:07:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1108241518500.4561@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4E54F793.3070904@gnu.org>
On Wed, 24 Aug 2011, Paolo Bonzini wrote:
> Would it make any sense to accept _Noreturn as an alternative spelling for the
> __noreturn__ attribute, in case someone is using the non-underscore-wrapped
> variant?
I suppose it might help some people use stdnoreturn.h, though I'm not
really sure stdnoreturn.h is that useful.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2011-08-24 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 22:00 Joseph S. Myers
2011-08-18 22:02 ` Gabriel Dos Reis
2011-08-19 14:19 ` Joseph S. Myers
2011-08-19 9:23 ` Richard Sandiford
2011-08-19 14:25 ` Rainer Orth
2011-08-24 10:55 ` Richard Sandiford
2011-08-24 13:27 ` Joseph S. Myers
2011-08-24 14:25 ` Catherine Moore
2011-08-24 14:10 ` Paolo Bonzini
2011-08-24 18:07 ` Joseph S. Myers [this message]
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=Pine.LNX.4.64.1108241518500.4561@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdsandiford@googlemail.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).