From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30641 invoked by alias); 29 Aug 2005 21:11:07 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 30548 invoked by uid 48); 29 Aug 2005 21:11:01 -0000 Date: Mon, 29 Aug 2005 21:27:00 -0000 Message-ID: <20050829211101.30546.qmail@sourceware.org> From: "falk at debian dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050829140226.23623.m.reszat@kostal.com> References: <20050829140226.23623.m.reszat@kostal.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug middle-end/23623] volatile keyword changes bitfield access size from 32bit to 8bit X-Bugzilla-Reason: CC X-SW-Source: 2005-08/txt/msg03383.txt.bz2 List-Id: ------- Additional Comments From falk at debian dot org 2005-08-29 21:10 ------- (In reply to comment #0) > Access to bf1.b is correctly done as 32-bits (lwz/stw opcodes), bf2.b is > accessed as 8-bits (lbz/stb opcodes). GCC3.4.3 shows the same behaviour, can't > go back any further. The same happens when the bitfield itself is made volatile, > not the whole struct. This is intentional. The idea is not to touch any more of that volatile stuff than absolutely needed. Why do you think it is a bug? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23623