From: Jim Meyering <jim@meyering.net>
To: Florian Weimer <fweimer@redhat.com>
Cc: 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: Sun, 18 Dec 2016 09:53:00 -0000 [thread overview]
Message-ID: <CA+8g5KETiBxY5jWavcHP7CWB6UnmdJDD+z2QnWMF=8csm_d5WA@mail.gmail.com> (raw)
In-Reply-To: <c78e8005-524d-336a-c719-9eb0f599f028@redhat.com>
On Fri, Dec 16, 2016 at 4:15 AM, Florian Weimer <fweimer@redhat.com> wrote:
> On 12/15/2016 01:24 AM, Jim Meyering 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
>> when required, but otherwise putting the expression as-is in an
>> "if"
>> expression (hence, with no added parentheses) within a statement
>> expression.
>
>
> Thanks. I just noticed your fb.com address in the ChangeLog. Do you know
> if Facebook have filed paperwork with the FSF for glibc? Commit
> 7ee03f00188723a4de2b85021e511ced6d7fc4be was just two lines, and this commit
> here only adds only very few significant source lines, too, so we might get
> away without the paperwork, but this is probably the last such change we can
> accept.
>
> Anyway, please install if you have commit access.
Thanks. Pushed.
I'll add glibc to my list for the next Facebook copyright assignment.
next prev parent reply other threads:[~2016-12-18 9:53 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 [this message]
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+8g5KETiBxY5jWavcHP7CWB6UnmdJDD+z2QnWMF=8csm_d5WA@mail.gmail.com' \
--to=jim@meyering.net \
--cc=fweimer@redhat.com \
--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).