Displaying 6 results from an estimated 6 matches for "setprefixdata".
Did you mean:
getprefixdata
2015 Oct 12
2
[RFC] Clean up the way we store optional Function data
...lse chime in on what they'd like to see?
>
> Sanjoy's idea makes sense to me, but only if we never need to add
> prefix/prologue data after functions are created. Are there any places
> where we need/want to add them after the fact?
I think so. I see:
LinkModules.cpp: Dst.setPrefixData(MapValue(Src.getPrefixData(), ValueMap,
BitcodeReader.cpp: FunctionPrologueWorklist.back().first->setPrologueData(C);
InlineFunction.cpp: Caller->setPersonalityFn(CalledPersonality);
Some of these sites could be refactored so that the Functions are created with the prefix/prologue data they...
2015 Oct 12
3
[RFC] Clean up the way we store optional Function data
...gt; Sanjoy's idea makes sense to me, but only if we never need to add
>>> prefix/prologue data after functions are created. Are there any places
>>> where we need/want to add them after the fact?
>>
>> I think so. I see:
>>
>> LinkModules.cpp: Dst.setPrefixData(MapValue(Src.getPrefixData(), ValueMap,
>> BitcodeReader.cpp: FunctionPrologueWorklist.back().first->setPrologueData(C);
>> InlineFunction.cpp: Caller->setPersonalityFn(CalledPersonality);
>>
>> Some of these sites could be refactored so that the Functions are create...
2015 Oct 12
2
[RFC] Clean up the way we store optional Function data
...> > >> prefix/prologue data after functions are created. Are there any
> places
> > >> where we need/want to add them after the fact?
> > >
> > > I think so. I see:
> > >
> > > LinkModules.cpp:
> Dst.setPrefixData(MapValue(Src.getPrefixData(), ValueMap,
> > > BitcodeReader.cpp:
> FunctionPrologueWorklist.back().first->setPrologueData(C);
> > > InlineFunction.cpp: Caller->setPersonalityFn(CalledPersonality);
> > >
> > > Some of these sites could...
2015 Oct 16
2
[RFC] Clean up the way we store optional Function data
...prefix/prologue data after functions are created. Are there any
>>> places
>>>>>> where we need/want to add them after the fact?
>>>>>
>>>>> I think so. I see:
>>>>>
>>>>> LinkModules.cpp:
>>> Dst.setPrefixData(MapValue(Src.getPrefixData(), ValueMap,
>>>>> BitcodeReader.cpp:
>>> FunctionPrologueWorklist.back().first->setPrologueData(C);
>>>>> InlineFunction.cpp: Caller->setPersonalityFn(CalledPersonality);
>>>>>
>>>>> Some of th...
2015 Oct 21
2
[RFC] Clean up the way we store optional Function data
...re there any
>>>>> places
>>>>>>>> where we need/want to add them after the fact?
>>>>>>>
>>>>>>> I think so. I see:
>>>>>>>
>>>>>>> LinkModules.cpp:
>>>>> Dst.setPrefixData(MapValue(Src.getPrefixData(), ValueMap,
>>>>>>> BitcodeReader.cpp:
>>>>> FunctionPrologueWorklist.back().first->setPrologueData(C);
>>>>>>> InlineFunction.cpp: Caller->setPersonalityFn(CalledPersonality);
>>>>>>>
&...
2015 Oct 12
2
[RFC] Clean up the way we store optional Function data
Hi Sanjoy,
> I don't know how prologue and prefix data is used -- is it correct to
> say that you're basically trying to give `llvm::Function` s some
> "optional" operands, and that you know during construction of an
> `llvm::Function` how many optional operands the `llvm::Function` will
> need[1]?
Yep. Though not operands exactly, since they wouldn't be in