From: Andreas Schwab <schwab@linux-m68k.org>
To: Jim Meyering <jim@meyering.net>
Cc: Florian Weimer <fweimer@redhat.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: Tue, 27 Dec 2016 17:47:00 -0000 [thread overview]
Message-ID: <87bmvxi7r3.fsf@linux-m68k.org> (raw)
In-Reply-To: <CA+8g5KG83STDuNKaUEhjYQAHNU5hm=+UdncBNn2hWRi0m2q6KQ@mail.gmail.com> (Jim Meyering's message of "Wed, 14 Dec 2016 16:24:30 -0800")
On Dez 14 2016, Jim Meyering <jim@meyering.net> wrote:
> Thanks. I didn't realize glibc used such a strict interpretation.
> Happy to adjust. How's this (also in the attached, rebased commit):
>
> Let gcc detect assert(a = 1) errors.
> * assert/assert.h (assert) Rewrite, retaining the old definintion
Missing colon.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-12-27 17:47 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
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 [this message]
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=87bmvxi7r3.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=fweimer@redhat.com \
--cc=jim@meyering.net \
--cc=libc-alpha@sourceware.org \
--cc=roland@hack.frob.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).