RFH: Impose code-movement restrictions and value assumption (for ASYNCHRONOUS/Coarrays)

[Ian Lance Taylor]

Tobias Burnus <burnus@net-b.de> writes:

> In that sense, I do not seem to need a new flags for
> asynchronous/coarrays - which are handled by TYPE_QUAL_RESTRICT, but I
> need a new flag for normal (noncoarray, nonasychronous) variables,
> which are passed by value or are allocatable - and where a function
> call won't affect the value.

Yes, sounds like it.  At first glance I don't think it should be a
TYPE_QUAL, I think it should be a flag on the DECL.

Ian