> I fully agree with you, the current default state of > -fstrict-volatile-bitfields should be disabled for all targets.
Please don't do that until gcc produces code that does the same things. Most of my targets rely on gcc not doing the old behavior, to generate correct code. > For portability of application code, the default should be always > off, unless specifically requested. The vendors of my targets specificially requested it be the default. > Even driver code rarely uses bit-fields for register access, People keep saying this, and people are wrong. For the targets I support, they *all* use bitfields for *all* the peripherals, because that's what's in the headers the vendor ships with each chip.
