> On Jan 5, 2015, at 1:24 PM, DJ Delorie <d...@redhat.com> wrote:
>
>
>> What is involved with the auditing?
>
> Each pattern that (directly or indirectly) uses general_operand,
> memory_operand, or nonimmediate_operand needs to be checked to see if
> it's volatile-safe. If so, you need to change the predicate to
> something that explicitly accepts volatiles.
>
> There's been talk about adding direct support for a "volatile-clean"
> flag that avoids this for targets where you know it's correct, which
> bypasses the volatile check in those functions, but it hasn't happened
> yet.
I looked in the documentation and didn’t see this described. Is it? Where?
A general flag seems useful, because for most targets it would seen applicable.
paul
