From: Jim Meyering <jim@meyering.net>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Zack Weinberg <zackw@panix.com>,
Roland McGrath <roland@hack.frob.com>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] assert.h: allow gcc to detect assert(a = 1) errors
Date: Sat, 26 Nov 2016 06:36:00 -0000 [thread overview]
Message-ID: <CA+8g5KEpx-U_+r92TASDMZ37w9kK9=Dytasu91GuM31H6pY6zA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611241310310.2194@digraph.polyomino.org.uk>
On Thu, Nov 24, 2016 at 5:12 AM, Joseph Myers <joseph@codesourcery.com> wrote:
> On Wed, 23 Nov 2016, Zack Weinberg wrote:
>
>> ... Would you please file a feature-request with the gcc people asking
>> for something that turns __extension__ back off? It would be nice to
>
> (Which I suggested in <https://gcc.gnu.org/ml/gcc/2001-04/msg00642.html> -
> note the point about counting nesting so this cancels exactly one
> enclosing __extension__.)
I made the feature request here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78539
next prev parent reply other threads:[~2016-11-26 6:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 19:12 Jim Meyering
2014-07-16 20:15 ` Roland McGrath
2014-07-16 20:44 ` Jim Meyering
2016-11-24 2:22 ` Jim Meyering
2016-11-24 2:59 ` Zack Weinberg
2016-11-24 13:13 ` Joseph Myers
2016-11-26 6:36 ` Jim Meyering [this message]
2016-11-24 7:36 ` Florian Weimer
2016-11-26 6:15 ` Jim Meyering
2016-12-09 3:21 ` Jim Meyering
2016-12-14 5:28 ` Jim Meyering
2016-12-14 9:13 ` Florian Weimer
2016-12-15 0:25 ` Jim Meyering
2016-12-16 12:15 ` Florian Weimer
2016-12-18 9:53 ` Jim Meyering
2016-12-27 17:47 ` Andreas Schwab
2016-12-28 12:50 ` Florian Weimer
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='CA+8g5KEpx-U_+r92TASDMZ37w9kK9=Dytasu91GuM31H6pY6zA@mail.gmail.com' \
--to=jim@meyering.net \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=roland@hack.frob.com \
--cc=zackw@panix.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).