On Wed, Sep 4, 2013 at 3:55 PM, DJ Delorie <d...@redhat.com> wrote: > >> How about this for a compromise: Let's make the default of >> -fstrict-volatile-bitfields an optional configure argument for gcc >> 4.9, that can be used for every target, even for X86_64 of you want ? > > I don't care how it's enabled (currently, each target that wants it, > sets it) as long as a plain "./configure" gives the correct defaults. > "Don't forget this option or your code won't work" isn't an option.
You mean the C++11 application or the driver? You mean -fstrict-volatile-bitfields or -fno-strict-volatile-bitfields? Not to think about C++11 drivers ;) Richard.
