From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6291 invoked by alias); 3 Oct 2002 19:18:18 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 6276 invoked from network); 3 Oct 2002 19:18:16 -0000 Received: from unknown (HELO mx2.redhat.com) (12.150.115.133) by sources.redhat.com with SMTP; 3 Oct 2002 19:18:16 -0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.11.6/8.11.6) with ESMTP id g93JI3s19087; Thu, 3 Oct 2002 15:18:03 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g93JIFl19177; Thu, 3 Oct 2002 15:18:15 -0400 Received: from localhost.localdomain (frothingslosh.sfbay.redhat.com [172.16.24.27]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g93JI9w07072; Thu, 3 Oct 2002 12:18:09 -0700 Received: (from rth@localhost) by localhost.localdomain (8.11.6/8.11.6) id g93JI4601956; Thu, 3 Oct 2002 12:18:04 -0700 X-Authentication-Warning: localhost.localdomain: rth set sender to rth@redhat.com using -f Date: Thu, 03 Oct 2002 12:59:00 -0000 From: Richard Henderson To: Philippe Trottier Cc: gcc@gcc.gnu.org, nathan@gcc.gnu.org Subject: Re: c/8131: Union of struct of union of struct bit field Message-ID: <20021003191804.GC1931@redhat.com> Mail-Followup-To: Richard Henderson , Philippe Trottier , gcc@gcc.gnu.org, nathan@gcc.gnu.org References: <20021003105049.844.qmail@sources.redhat.com> <5AC076D0-D6C0-11D6-A2DC-00306543F85E@invers.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5AC076D0-D6C0-11D6-A2DC-00306543F85E@invers.fi> User-Agent: Mutt/1.4i X-SW-Source: 2002-10/txt/msg00178.txt.bz2 On Thu, Oct 03, 2002 at 02:07:49PM +0300, Philippe Trottier wrote: > I filed this bug, but seems the definition says it is not a bug. > Anyone here could tell me How to handle a case where 1 bit can decide > the format of a 32 bit word ? Push the one bit down into each structure. If it's at the same place in each structure, then it doesn't matter which one you access to examine it. r~