public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de To: gcc-gnats@gcc.gnu.org Subject: c/8420: volatile after the type specifier for an unnamed structure is rejected Date: Fri, 01 Nov 2002 02:16:00 -0000 [thread overview] Message-ID: <20021101101409.13596.qmail@sources.redhat.com> (raw) >Number: 8420 >Category: c >Synopsis: volatile after the type specifier for an unnamed structure is rejected >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Fri Nov 01 02:16:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Christian Ehrhardt >Release: gcc-3.2 >Organization: >Environment: theseus$ uname -a SunOS theseus 5.9 Generic_112233-02 sun4u sparc SUNW,Ultra-4 theseus$ gcc -v Reading specs from /usr/local/bin/../lib/gcc-lib/sparc-sun-solaris2.9/3.2/specs Configured with: /export/local/manager/playground/ULMgcc32/src/gcc-3.2/configure --with-ld=/usr/local/bin/ld --with-gnu-ld --with-as=/usr/local/bin/as --with-gnu-as --prefix=/usr/local/ Thread model: posix gcc version 3.2 >Description: This source file is rejected: struct a { struct { int x; } volatile a; }; /* OK */ struct b { volatile struct { int x; } ; }; /* OK */ struct c { struct { int x; } volatile; }; /* ERROR */ theseus$ gcc -Wall -c t.c t.c:10: unnamed fields of type other than struct or union are not allowed This code is made up to demonstrate a problem found while reading the source: grokfield is called for a field declaration without an identifier and tries to check that the field type is a structure or union. However, grokfield assumes that the type specifier is the first element in the list passed as declspecs which is not necessarily true. Given the other two examples (struct a and struct b) which are accepted this code should probably be legal. Even if it is illegal the error message is wrong. >How-To-Repeat: See description above. >Fix: A workaround is to move the volatile keyword before the struct. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-11-01 10:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-01 2:16 ehrhardt [this message] 2002-12-02 13:09 bangerth 2002-12-11 15:46 Richard Henderson 2002-12-11 16:36 Christian Ehrhardt
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=20021101101409.13596.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --cc=gcc-gnats@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).