public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55227] designated initializer for char array by string constant Date: Sun, 24 Oct 2021 15:54:56 +0000 [thread overview] Message-ID: <bug-55227-4-52Mzy64DoX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55227-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55227 Will Wray <wjwray at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wjwray at gmail dot com --- Comment #6 from Will Wray <wjwray at gmail dot com> --- Hit this in implementing P1997 array copy semantics (which generalizes the char-array <- string-literal case to array <- array initialization). Compiler Explorer link https://godbolt.org/z/vednE3bYz The reshape_init_r code that ensadc points to is one problem. The code effectively special-cases the C rule that allows optional braces around a string-literal initializer: A brace-enclosed string-literal initializer has its braces stripped, but then the code does not account at all for nested designators (as a recursive call to reshape_init would or should do). This can be seen in the way that bogus nested designators are ignored: struct C {char a[2];} C y = {{.bogus="y"}}; // Invalid, g++ accepts C z = {{[0]="z"}}; // Invalid, g++ accepts (pedantic warning GNU [0]) (so the 'solution' of adding braces is misleading, non-standard, non-portable). Then, in placing the designator correctly outside the braces, it is not matched with the brace-enclosed initializer (haven't tracked down why yet): C w = {.a={"w"}}; // Valid, g++ rejects designated braced // (gcc C accepts) (other C++ compilers accept) A second problem is that the 'matching' of designator to initializer is brittle even without optional braces; only the exactly-matching char-array type (i.e. and extent) is accepted in an unbraced string literal: C u = {.a="u"}; // Valid, designated char[2] literal for char[2] field C r = {.a=""}; // Valid, g++ rejects designated char[1] for char[2] A workaround is to match the size of the char array by padding with zeros: C r = {.a="\0"}; I've spent over a day trying to isolate the 'matching' issue - could do with assist from a designated-initializer mechanic.
next prev parent reply other threads:[~2021-10-24 15:54 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-07 8:27 [Bug c++/55227] New: " pavel.v.chupin at gmail dot com 2012-11-07 22:25 ` [Bug c++/55227] " daniel.kruegler at googlemail dot com 2020-04-08 10:11 ` ensadc at mailnesia dot com 2020-06-16 11:40 ` steven.spark at gmail dot com 2021-10-24 15:54 ` wjwray at gmail dot com [this message] 2021-10-24 21:25 ` wjwray at gmail dot com 2021-10-24 21:31 ` wjwray at gmail dot com 2021-10-25 17:06 ` wjwray at gmail dot com 2021-10-25 17:44 ` wjwray at gmail dot com 2021-11-04 23:43 ` wjwray at gmail dot com 2021-11-07 0:27 ` pinskia at gcc dot gnu.org 2021-11-18 3:17 ` wjwray at gmail dot com 2021-11-18 3:21 ` wjwray at gmail dot com 2021-12-14 5:34 ` pinskia at gcc dot gnu.org 2022-01-23 22:27 ` cvs-commit at gcc dot gnu.org
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=bug-55227-4-52Mzy64DoX@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).