patch: honor volatile bitfield types

[Jeff Law]

On 06/11/10 10:15, Mark Mitchell wrote:
> DJ Delorie wrote:
>
>    
>>> Shouldn't the default actually be target-specific (no new hooks needed,
>>> existing hooks to set options in a target-specific way should suffice,
>>> though maybe you need to initialize the flag setting to -1 to allow
>>> OVERRIDE_OPTIONS to know whether it was explicitly set)?  For example, ARM
>>> EABI should enable this by default.
>>>        
>> Yes, it should.  I figured, let's get the functionality working first,
>> then let the target maintainers decide which targets need it on and
>> which off.
>>      
> Very glad to see this functionality.  However, before it goes in, I
> think the change that Joseph is suggesting (which is perhaps just a
> documentation change to say that the default is target-dependent) shold
> occur.
>    
Right.  Just to be clear, I asked DJ to make this a -f flag rather than 
a -m flag and that for targets where it should be the default (ARM EABI) 
the backend should arrange  for the flag to be turned on by default.

jeff