search for: mrjamesstark

...and grab the scope + > line/column that way for each instruction. You can see the format of each > metadata node by looking at DebugInfo.h. Hope this helps, feel free to send > mail if you have any more questions. > > -eric > > On Wed Jan 22 2014 at 8:59:36 PM, James Stark <mrjamesstark at gmail.com> > wrote: > >> Hi, >> >> I have bitcode files built by LLVM v3.3 and need to process them using >> v3.4 tools. While I don't expect a lot of backward compatibility in LLVM, >> luckily it seems everything's working fine, except for reading...

Hi, My pass scans call instructions for standard C library calls. For some libc functions, however, LLVM uses intrinsics instead. For example, I see that my memcpy calls are replaced by the llvm.memcpy.* intrinsics. This is not a problem because I can simply look for llvm.memcpy calls when scanning for memcpy calls. The problem arises when LLVM implicitly inserts llvm.memcpy intrinsics into my

Hi, I have bitcode files built by LLVM v3.3 and need to process them using v3.4 tools. While I don't expect a lot of backward compatibility in LLVM, luckily it seems everything's working fine, except for reading source line information attached to instructions. I use this piece of code [0] to get source line information. For v3.4, instruction.getMetadata returns NULL. I used llvm-dis to