public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pthomas@suse.de
To: gcc-gnats@gcc.gnu.org
Cc: aj@suse.de
Subject: c/10225: Unnamed structs aren't handled correctly in 3.3
Date: Wed, 26 Mar 2003 17:16:00 -0000	[thread overview]
Message-ID: <20030326170948.7631.qmail@sources.redhat.com> (raw)


>Number:         10225
>Category:       c
>Synopsis:       Unnamed structs aren't handled correctly in 3.3
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 26 17:16:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     pthomas@suse.de
>Release:        3.3 20030325 (prerelease)
>Organization:
>Environment:
x86_64-suse-linux
>Description:
When compiling the attached unnamed2.c with 3.3 mainline,
the code is rejected:

unnamed2.c:9: warning: declaration does not declare anything
unnamed2.c: In function `main':
unnamed2.c:16: error: structure has no member named `z'

Whereas 3.2.2 accepts the code, so this is clearly a regression.

Note that the ntfs driver in Linux kernel 2.5.65 uses this extension and thus breaks when compiled with 3.3.

>How-To-Repeat:
Compile the attached code.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-csrc; name="unnamed2.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="unnamed2.c"

dHlwZWRlZiBzdHJ1Y3QKewoJaW50IHo7Cn10eXBlX3o7CiAgCnN0cnVjdCBCCnsKCWludCBpOwoJ
dHlwZV96Owp9OwoKCmludCBtYWluKHZvaWQpCnsKCXN0cnVjdCBCIEI7CglCLnogPSAxOwoKCXJl
dHVybiAwOwp9Cg==


             reply	other threads:[~2003-03-26 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 17:16 pthomas [this message]
2003-03-26 17:27 Steven Bosscher
2003-03-26 17:46 Philipp Thomas

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=20030326170948.7631.qmail@sources.redhat.com \
    --to=pthomas@suse.de \
    --cc=aj@suse.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: 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).