This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/23623] volatile keyword changes bitfield access size from 32bit to 8bit
- From: "m dot reszat at kostal dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Sep 2005 15:12:52 -0000
- Subject: [Bug middle-end/23623] volatile keyword changes bitfield access size from 32bit to 8bit
- References: <20050829140226.23623.m.reszat@kostal.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From m dot reszat at kostal dot com 2005-09-08 15:12 -------
(In reply to comment #6)
> (In reply to comment #5)
> > I will try and dig up the EABI for PowerPC
> > > Note this also happens on ARM where (in the EABI) it is definitely a bug
None of the documents I found makes a statement as clear as the ARM EABI does.
Can someone point me to the source file where the "narrowing" is done, to maybe
simply "comment it out"?; I don't feel capable of providing a real fix, see
below, but I also don't want to rewrite large portions of my code when migrating
to GCC.
Having given more thought to the problem, isn't the "narrowing" an optimization
which should not be a fixed property of the compiler, given that even for the
same type of machine ("target") there can exist various different memory
interfaces? Hence, shouldn't it be an optimization option, "on" by default to be
backwards compatible?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23623