search for: dedundant

Hi, Could any one please tell me if there is any way to remove 11 letters long cryptic output from -ii option. I am using rsync 3.0.5 rsync -av -stats -ii --log-file-format='CONTENTS: %i %f %l %o %b' --log-file='/tmp/rsync-test' Mydocs/ Mydocs1/" The output of this command: 2009/03/31 15:15:17 [4537] building file list 2009/03/31 15:15:29 [4537] created directory Mydocs1

...it has no name, the AsmWriter emits a number ("%0"), by counting from the top. The only other locals could be function arguments, and instnamer names those too. > So there really is no way to do this shy of creating (or basically > copying) the API from AsmWriter (seems very dedundant to me)? This seems > like a large failing? Correct, you'd have to copy that logic. It's not a large failing because nobody uses names of non-globals for anything. When we want to refer to a value, we use the Value*. Nick > > On Fri, Oct 21, 2011 at 7:03 PM, Nick Lewycky <ni...

..., Unfortunately this doesn't answer my question I don't think. It seems that -instnamer, as you mention, names the instructions but still does not name the local variables. So there really is no way to do this shy of creating (or basically copying) the API from AsmWriter (seems very dedundant to me)? This seems like a large failing? On Fri, Oct 21, 2011 at 7:03 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Ryan Taylor wrote: > >> It looks like the AsmWriter is generating the local variables (SlotNum)s >> on the fly in that file (AsmWriter.cpp), so is there any...

It looks like the AsmWriter is generating the local variables (SlotNum)s on the fly in that file (AsmWriter.cpp), so is there any way at all to get this information from the operation itself, via Instruction, Value or Type? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111021/55f4887c/attachment.html>

Ryan Taylor wrote: > It looks like the AsmWriter is generating the local variables (SlotNum)s > on the fly in that file (AsmWriter.cpp), so is there any way at all to > get this information from the operation itself, via Instruction, Value > or Type? Nope! As you noticed, they're created on the fly... ...when the Value or Type is anonymous. If you want them to be persistent,

...t;>> instnamer >>> names those too. >>> >>> >>> So there really is no way to do this shy of creating >>> (or >>> basically >>> copying) the API from AsmWriter (seems very dedundant to >>> me)? >>> This seems >>> like a large failing? >>> >>> >>> Correct, you'd have to copy that logic. >>> >>> It's not a large failing because nobody uses na...

...0"), by counting from the top. > The only other locals could be function arguments, and instnamer > names those too. > > > So there really is no way to do this shy of creating (or > basically > copying) the API from AsmWriter (seems very dedundant to me)? > This seems > like a large failing? > > > Correct, you'd have to copy that logic. > > It's not a large failing because nobody uses names of non-globals > for anything. When we want to refer to a value, we use the Value*. > >...

...The only other locals could be function arguments, and instnamer > names those too. > > > So there really is no way to do this shy of creating (or > basically > copying) the API from AsmWriter (seems very dedundant to > me)? > This seems > like a large failing? > > > Correct, you'd have to copy that logic. > > It's not a large failing because nobody uses names of > non-globals > for anythi...

...t;>>> >>>>>> >>>>>> So there really is no way to do this shy of >>>>>> creating (or >>>>>> basically >>>>>> copying) the API from AsmWriter (seems very dedundant >>>>>> to >>>>>> me)? >>>>>> This seems >>>>>> like a large failing? >>>>>> >>>>>> >>>>>> Correct, you'd have to copy tha...

...gt;> >>>>>>>> So there really is no way to do this shy of >>>>>>>> creating (or >>>>>>>> basically >>>>>>>> copying) the API from AsmWriter (seems very dedundant >>>>>>>> to >>>>>>>> me)? >>>>>>>> This seems >>>>>>>> like a large failing? >>>>>>>> >>>>>>>> >>>>>&gt...