This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PING: Default to -fstrict-volatile-bitfields for ARM EABI


> If -fstrict-volatile-bitfields is off, it's possible for GCC to use an 
> 8-bit, 16-bit or 32-bit insn to access such bit-field. It depends on 
> which one GCC think is most efficient. If you expect using an 8-bit 
> insn, you need to declare it having unsigned char (if it's 8-bit in that 
> target) as the container type and turn -fstrict-volatile-bitfields on.

Ah, so "container type" means the type that's present in the declaration,
not the type of the entire struct.  I'd suggest clarifying the documentation.
I agree with Mark, though. That's a separate issue.  You're not making it
worse: the documentation made it harder to review the patch.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]