Displaying 9 results from an estimated 9 matches for "valuetovaluemap".
Did you mean:
valuetovaluemapty
2011 May 08
1
[LLVMdev] Change the return type of a function
Thanks John for the reply. Ya, I took a similar approach. I cloned the
entire
function using CloneFunctionInto() in Cloning.h.
Now, I am facing a new Problem. I am not able to understand the concept of
ValueToValueMap. I am trying to figure it out by testing it. But I am
getting
errors like "Referring to an argument in another function!". I am not able
to get
good examples nor good documentation on ValueToValueMap. Can you point
me in the right direction ?
On Sun, May 8, 2011 at 5:06 AM, John Criswel...
2015 Mar 19
2
[LLVMdev] RFC: Loop versioning for LICM
...r the loop-distribution pass in http://reviews.llvm.org/D6930 <http://reviews.llvm.org/D6930>.
>
> Please let me know if you have any questions.
>
> I have gone through current LAA, found few gaps for reusing it.
>
> i.e.
> 928 void LoopAccessInfo::analyzeLoop(const ValueToValueMap &Strides) {
> 1029 if (isUniform(Ptr)) {
> 1030 emitAnalysis(
> 1031 LoopAccessReport(ST)
> 1032 << "write to a loop invariant address could not be vectorized");
> 1033 DEBUG(dbgs() << "LAA: We don't allow storing...
2015 Mar 20
2
[LLVMdev] RFC: Loop versioning for LICM
...r the loop-distribution pass in http://reviews.llvm.org/D6930 <http://reviews.llvm.org/D6930>.
>
> Please let me know if you have any questions.
>
> I have gone through current LAA, found few gaps for reusing it.
>
> i.e.
> 928 void LoopAccessInfo::analyzeLoop(const ValueToValueMap &Strides) {
> 1029 if (isUniform(Ptr)) {
> 1030 emitAnalysis(
> 1031 LoopAccessReport(ST)
> 1032 << "write to a loop invariant address could not be vectorized");
> 1033 DEBUG(dbgs() << "LAA: We don't allow storing...
2015 Mar 24
3
[LLVMdev] RFC: Loop versioning for LICM
...r the loop-distribution pass in http://reviews.llvm.org/D6930 <http://reviews.llvm.org/D6930>.
>
> Please let me know if you have any questions.
>
> I have gone through current LAA, found few gaps for reusing it.
>
> i.e.
> 928 void LoopAccessInfo::analyzeLoop(const ValueToValueMap &Strides) {
> 1029 if (isUniform(Ptr)) {
> 1030 emitAnalysis(
> 1031 LoopAccessReport(ST)
> 1032 << "write to a loop invariant address could not be vectorized");
> 1033 DEBUG(dbgs() << "LAA: We don't allow storing...
2011 May 07
0
[LLVMdev] Change the return type of a function
On 5/7/11 2:01 PM, Gokul Ramaswamy wrote:
> Hello All,
>
> I want to change the return type of a function in a Pass(in a
> module Pass). I dont want to change any of the arguments of that function.
> Assume that, I can handle the returning values properly inside the
> function. Please guide me how to do this ?
You need to do the following steps:
1) Create a new function
2011 May 07
2
[LLVMdev] Change the return type of a function
Hello All,
I want to change the return type of a function in a Pass(in a module
Pass). I dont want to change any of the arguments of that function.
Assume that, I can handle the returning values properly inside the function.
Please guide me how to do this ?
--
Regards,
Gokul Ramaswamy,
Graduate Student,
Department of CSE, IIT Bombay
http://www.cse.iitb.ac.in/~ramaswamy
--------------
2013 Jun 10
0
[LLVMdev] CFG of a function
...of you pass). If you call eraseFromParent,
then all the instruction, BB's, arguments, and everything you cloned will
be deleted from memory, and it'll just seem like nothing was cloned.
Ok, now in order to identify all the values between the two copies of the
functions you need to use that ValueToValueMap that you created and used as
an argument for cloneFunction. This VMap can be seen as a hash of values,
and everything in the cloned function is mapped to something in the
original function inside this map. So, if you need to identify an
equivalent BB between them, for example, you could use VMap[BB...
2015 Mar 11
2
[LLVMdev] RFC: Loop versioning for LICM
> On Mar 5, 2015, at 10:33 PM, Nema, Ashutosh <Ashutosh.Nema at amd.com> wrote:
>
>
> I am about to post the patches to make LAA suitable for Loop Distribution. As you will hopefully find this will make the LAA more generic. I will cc you on the patches.
>
> Sure Adam.
>
> RuntimeCheckEmitter
> âRuntimeCheckEmitter::addRuntimeCheckâ
> While creating
2013 Jun 06
3
[LLVMdev] CFG of a function
I think I understood that, but what I mean is what is the function
responsible to do mapping is it MapValue() in ValueMapper.h?
Thanks for your help
On 6 June 2013 09:54, Alexandru Ionut Diaconescu <
alexandruionutdiaconescu at gmail.com> wrote:
> Map every basic block from the CFG to a set of integers. The successors
> from the CFG can be used to make the edges in your simplified