public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/52182] New: unnamed structs/unions are supported by ISO C99 Date: Thu, 09 Feb 2012 09:20:00 -0000 [thread overview] Message-ID: <bug-52182-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52182 Bug #: 52182 Summary: unnamed structs/unions are supported by ISO C99 Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: jan.kratochvil@redhat.com http://gcc.gnu.org/onlinedocs/gcc/Unnamed-Fields.html#Unnamed-Fields says "As permitted by ISO C11" and also: echo 'struct { int a; struct { int b; }; } s;'|gcc -c -x c - -Wall -std=c99 -pedantic <stdin>:1:34: warning: ISO C99 doesn’t support unnamed structs/unions [-pedantic] FAIL: gcc (GCC) 4.6.3 20120209 (prerelease) FAIL: gcc (GCC) 4.7.0 20120209 (experimental) plus FAIL: gcc (GCC) 4.4.7 20120209 (prerelease) FAIL: gcc (GCC) 4.5.4 20120209 (prerelease) print <stdin>:1:34: warning: declaration does not declare anything But ISO C99 says: A structure type describes a sequentially allocated nonempty set of member objects (and, in certain circumstances, an incomplete array), each of which has an optionally specified name and possibly distinct type. ^^^^^^^^^^^^^^^^^^^^^^^^^ A union type describes an overlapping nonempty set of member objects, each of which has an optionally specified name and possibly distinct type. ^^^^^^^^^^^^^^^^^^^^^^^^^ (I agree ISO C90 spec still did not support unnamed fields.)
next reply other threads:[~2012-02-09 9:20 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-09 9:20 jan.kratochvil at redhat dot com [this message] 2012-02-09 17:24 ` [Bug c/52182] " joseph at codesourcery dot com 2012-02-09 17:43 ` jan.kratochvil at redhat dot com
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-52182-4@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).