patch [6/5] check for conflict with -fstrict-volatile-bitfields and -std=

Sandra Loosemore sandra@codesourcery.com
Wed Jun 19 20:33:00 GMT 2013


On 06/17/2013 06:02 PM, Sandra Loosemore wrote:
>
> I had another thought:  perhaps -fstrict-volatile-bitfields could remain
> the default on targets where it currently is, but it can be overridden
> by an appropriate -std= option.  Perhaps also GCC could give an error if
> -fstrict-volatile-bitfields is given explicitly with an incompatible
> -std= option.

Like this.  This patch is intended to be applied on top of the other 5 
pieces in this series, although in theory it's independent of them.  OK 
to commit, and does this resolve the objection to part 3?

-Sandra



-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitfields-6.log
Type: text/x-log
Size: 301 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20130619/2be30b8b/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitfields-6.patch
Type: text/x-patch
Size: 1618 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20130619/2be30b8b/attachment-0001.bin>


More information about the Gcc-patches mailing list