[patch 4/4] -fstrict-volatile-bitfields cleanup v3: remove from defaults on all targets

[Sandra Loosemore]

Since my previous idea of resolving conflicts between 
-fstrict-volatile-bitfields behavior and the new C/C++ memory model 
depending on the selected -std= option was shot down

http://gcc.gnu.org/ml/gcc-patches/2013-06/msg01163.html

it appears that the only way to make -fstrict-volatile-bitfields do 
something remotely resembling what it is supposed to do in a way that is 
acceptable to the maintainers is to make it not be the default on any 
target any more, so that the new memory model always takes precedence 
over ABI specifications by default.  So, here is a patch to do it.

The affected targets are aarch64, arm, h8300, m32c, rx, and sh.  The 
code change is identical on all targets, but I have only been able to 
test on arm (arm-none-eabi).  I have included tweaks to pass 
-fstrict-volatile-bitfields explicitly on the test cases that failed 
when the default was removed.  It might be that some tests for other 
targets need similar changes as well.

OK to commit in conjunction with the other patches in this series?

-Sandra

-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitfields-v3-4.log
Type: text/x-log
Size: 815 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20130701/d4e549ec/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitfields-v3-4.patch
Type: text/x-patch
Size: 6601 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20130701/d4e549ec/attachment-0001.bin>