Displaying 5 results from an estimated 5 matches for "winfer".
Did you mean:
infer
2012 Aug 21
0
[LLVMdev] Let's get rid of neverHasSideEffects
...;t set, TableGen should complain.
>
> I can't just kill off the neverHasSideEffects flag, that could cause miscompilations by clearing the UnmodeledSideEffects bit on instructions that should have it.
>
> Any suggestions for a clean transition? I was thinking about first adding a -Winfer flag that warns whenever TableGen infers a property that wasn't already set in the .td file.
>
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...
2012 Aug 22
2
[LLVMdev] Let's get rid of neverHasSideEffects
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 t...
2012 Aug 21
8
[LLVMdev] Let's get rid of neverHasSideEffects
...sSideEffects isn't set, TableGen should complain.
I can't just kill off the neverHasSideEffects flag, that could cause miscompilations by clearing the UnmodeledSideEffects bit on instructions that should have it.
Any suggestions for a clean transition? I was thinking about first adding a -Winfer flag that warns whenever TableGen infers a property that wasn't already set in the .td file.
/jakob
2012 Aug 24
0
[LLVMdev] Let's get rid of neverHasSideEffects
On Aug 22, 2012, at 9:40 AM, Evandro Menezes <emenezes at codeaurora.org> wrote:
> 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...
2012 Aug 21
0
[LLVMdev] Let's get rid of neverHasSideEffects
...;t set, TableGen should complain.
>
> I can't just kill off the neverHasSideEffects flag, that could cause miscompilations by clearing the UnmodeledSideEffects bit on instructions that should have it.
>
> Any suggestions for a clean transition? I was thinking about first adding a -Winfer flag that warns whenever TableGen infers a property that wasn't already set in the .td file.
>
> /jakob
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/m...