[LLVMdev] Let's get rid of neverHasSideEffects

[Evandro Menezes]

On 08/21/12 16:49, Jim Grosbach wrote:
>
> I like that. Possibly with the addition that we can filter by a specific property. -Winfer=neverHasSideEffects, e.g., would only show when that specific property is inferred.
>
> Beyond that, I don't see an alternative to an audit of the instructions that get flagged by such a warning. :(

This proposal would certainly make my life easier by having an easier to 
maintain insn table.

For instance, we had to create two store insn classes: one which defined 
mayStore and one that didn't.  The former was to be used when an insn 
had no pattern and the latter, when mayStore was implied in the pattern.

If only TableGen wouldn't warn about non-conflicting attributes at least...

-- 
Evandro Menezes          Austin, TX          emenezes at codeaurora.org
Qualcomm Innovation Center, Inc is a member of the Code Aurora Forum