From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26055 invoked by alias); 20 Jan 2011 13:00:11 -0000 Received: (qmail 26038 invoked by uid 22791); 20 Jan 2011 13:00:10 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 20 Jan 2011 13:00:04 +0000 From: "jengelh at medozas dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/47376] New: Duplicate member through anonymous unions not reported X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jengelh at medozas dot de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Thu, 20 Jan 2011 13:17:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-01/txt/msg02041.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47376 Summary: Duplicate member through anonymous unions not reported Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: jengelh@medozas.de Host: x86_64-suse-linux Target: x86_64-suse-linux Build: x86_64-suse-linux Given the following example: --- struct foo { int a; union { int a; double b; }; }; int main(void) { struct foo f; f.a = 123; return 0; } --- How it came to be: Accidental error where I had forgotten to remove foo.a after having added foo.{anonymous}.a. What has been observed: It compiles fine, which caused this programming error of mine to go unnoticed for half a day. It seems gcc gives foo.a precedence over foo.{anonymous}.a when accessing it through f.a=.... What had been expected: I would have liked that gcc emit at least a warning because f.a is ambiguous.