From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Matheus Castanho <msc@linux.ibm.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v12 1/2] Add 'codepoint_collation' support for LC_COLLATE.
Date: Mon, 6 Sep 2021 21:28:13 -0400 [thread overview]
Message-ID: <d52f9dd4-b14e-ddf7-dd6a-26905fb6cf51@redhat.com> (raw)
In-Reply-To: <87wnntwr3t.fsf@oldenburg.str.redhat.com>
On 9/6/21 1:28 PM, Florian Weimer wrote:
> * Matheus Castanho:
>
>> glibc doesn't build after this patch went in, looks like the assert
>> message is missing:
>>
>> In file included from C-collate.c:22:
>> C-collate-seq.c:58:42: error: expected ‘,’ before ‘)’ token
>> _Static_assert (sizeof (collseqmb) == 256);
>
> Sorry, I missed that. I'm testing a patch.
Thanks for committing a fix for this. I'm using too new compilers
and thinking in too new C :-)
I missed it too, C++ allows the assertion with an expression only
but current C11 does not. That's an annoying wrinkle fixed in C2x
which allows a one-argument version of _Static_assert.
This behaviour changed between gcc 8.5 and 9.1 where in 9.1 under
-std=c11 started accepting the 1-argument-form _Static_assert.
All of our CI/CD is using gcc 11, and I'm using gcc 10, so we would
not have seen this. Seems like we need another CI/CD trybot with
gcc 6.2!
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-09-07 1:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 15:43 [PATCH v12 0/2] C.UTF-8 Carlos O'Donell
2021-09-06 15:43 ` [PATCH v12 1/2] Add 'codepoint_collation' support for LC_COLLATE Carlos O'Donell
2021-09-06 17:20 ` Matheus Castanho
2021-09-06 17:28 ` Florian Weimer
2021-09-07 1:28 ` Carlos O'Donell [this message]
2021-09-07 1:57 ` Carlos O'Donell
2021-09-20 12:49 ` Matheus Castanho
2021-09-20 12:54 ` Carlos O'Donell
2021-09-06 15:43 ` [PATCH v12 2/2] Add generic C.UTF-8 locale (Bug 17318) Carlos O'Donell
2022-01-26 2:44 ` Michael Hudson-Doyle
2022-01-28 16:42 ` Carlos O'Donell
2022-01-30 23:58 ` Michael Hudson-Doyle
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=d52f9dd4-b14e-ddf7-dd6a-26905fb6cf51@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=msc@linux.ibm.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).