Displaying 6 results from an estimated 6 matches for "writeid".
Did you mean:
writed
2014 Feb 18
2
[LLVMdev] Question about per-operand machine model
...something to modify on tablegen? I think that the 'WriteResourceID' field of 'MCWriteLatencyEntry' is for identifying the WriteResources of each defintion as commented on code. As you know, tablegen sets the 'WriteResourceID' field of 'MCWriteLatencyEntry' with 'WriteID' when the 'Write' of defition is referenced by a 'ReadAdvance'. If we always set this field with 'WriteID', it causes problem? I can see that 'ReadAdvance' only uses the 'WriteResourceID' field of 'MCWriteLatencyEntry' in 'computeOperandLatenc...
2014 Feb 18
2
[LLVMdev] Question about per-operand machine model
Hi Andy and all,
I have a question about per-operand machine model. I am finding some
relations between 'MCWriteLatencyEntry' and 'MCWriteProcResEntry'.
For example,
class InstTEST<..., InstrItinClass itin> : Instruction {
let Itinerary = Itin;
}
// I assume this MI writes 2 registers.
def TESTINST : InstTEST<..., II_TEST>
// schedule info
II_TEST:
2014 Feb 19
2
[LLVMdev] Question about per-operand machine model
...think that the
>> 'WriteResourceID' field of 'MCWriteLatencyEntry' is for identifying
>> the WriteResources of each defintion as commented on code. As you
>> know, tablegen sets the 'WriteResourceID' field of
>> 'MCWriteLatencyEntry' with 'WriteID' when the 'Write' of defition is
>> referenced by a 'ReadAdvance'. If we always set this field with
>> 'WriteID', it causes problem? I can see that 'ReadAdvance' only uses
>> the 'WriteResourceID' field of 'MCWriteLatencyEntry' i...
2014 Feb 28
2
[LLVMdev] Question about per-operand machine model
...'WriteResourceID' field of 'MCWriteLatencyEntry' is for identifying
>>>> the WriteResources of each defintion as commented on code. As you
>>>> know, tablegen sets the 'WriteResourceID' field of
>>>> 'MCWriteLatencyEntry' with 'WriteID' when the 'Write' of defition is
>>>> referenced by a 'ReadAdvance'. If we always set this field with
>>>> 'WriteID', it causes problem? I can see that 'ReadAdvance' only uses
>>>> the 'WriteResourceID' field of 'MC...
2014 Mar 03
2
[LLVMdev] Question about per-operand machine model
...; field of 'MCWriteLatencyEntry' is for identifying
>>>>>> the WriteResources of each defintion as commented on code. As you
>>>>>> know, tablegen sets the 'WriteResourceID' field of
>>>>>> 'MCWriteLatencyEntry' with 'WriteID' when the 'Write' of defition is
>>>>>> referenced by a 'ReadAdvance'. If we always set this field with
>>>>>> 'WriteID', it causes problem? I can see that 'ReadAdvance' only uses
>>>>>> the 'WriteResource...
2014 Mar 04
2
[LLVMdev] Question about per-operand machine model
...atencyEntry' is for identifying
>>>>>>>> the WriteResources of each defintion as commented on code. As you
>>>>>>>> know, tablegen sets the 'WriteResourceID' field of
>>>>>>>> 'MCWriteLatencyEntry' with 'WriteID' when the 'Write' of defition is
>>>>>>>> referenced by a 'ReadAdvance'. If we always set this field with
>>>>>>>> 'WriteID', it causes problem? I can see that 'ReadAdvance' only uses
>>>>>>>>...