search for: dbgstoppointinst

Hi folks, I had some code that used to work fine in earlier versions of LLVM, but is now failing. I have some code that expands DbgStopPointInst instructions to my own entry points in an opt pass, but it's currently failing to get the file name and path back, though it is still correctly getting line numbers. If you happen to have a code fragment that is known to work, it would be much appreciated. What it used to work was call...

On Wed, Apr 29, 2009 at 6:04 PM, Sarah Thompson <sarah at findatlantis.com> wrote: > Hi folks, > > I had some code that used to work fine in earlier versions of LLVM, > but is now failing. I have some code that expands DbgStopPointInst > instructions to my own entry points in an opt pass, but it's currently > failing to get the file name and path back, though it is still > correctly getting line numbers. If you happen to have a code fragment > that is known to work, it would be much appreciated. > Hi Sarah, I&...

...at 6:29 PM, Bill Wendling wrote: > On Wed, Apr 29, 2009 at 6:04 PM, Sarah Thompson <sarah at findatlantis.com > > wrote: >> Hi folks, >> >> I had some code that used to work fine in earlier versions of LLVM, >> but is now failing. I have some code that expands DbgStopPointInst >> failing to get the file name and path back, though it is still >> correctly getting line numbers. If you happen to have a code fragment >> that is known to work, it would be much appreciated. >> > Hi Sarah, > > I'm not sure if this will help you out, but take...

On 2009-09-24 22:34, hc2428 at columbia.edu wrote: > Dear developers, > When I try to map line numbers in source code back to LLVM > basicblocks, I meet some problems: there is a source file with 1500 > lines of code, but when I use BasicBlockPass to collect all > DbgStopPoint instructions in this file, I can only get 500 lines of code. > The source code and the collected

...t; #include <cstdio> #include <set> #include <algorithm> @@ -86,6 +87,11 @@ // Ignore PHI nodes in the header. } else if (I->hasOneUse() && I->use_back() == Term) { // Ignore instructions only used by the loop terminator. + } else if (DbgStopPointInst *SPI = dyn_cast<DbgStopPointInst>(I)) { + // Ignore debug stop point instructions. + + // TODO: Ignore other debug instructions once they are defined + // in IntrinsicInst.h } else { ++Size; } -- Michael McCracken UCSD CSE PhD Student San D...

...de on that source line. I'd suggest an approach like this: Given an instruction in the a basic block, scan up and/or down the basic block, stopping at the first llvm.dbg.stoppoint instruction. Something like this should work: #include "llvm/IntrinsicInst.h" ... for (...) if (DbgStopPointInst *SP = dyn_cast<DbgStopPointInst>(Inst)) std::cerr << "Loc: " << SP->getFileName() << ":" << SP->getLine() << "\n"; If you look at IntrinsicInst, you'll see methods to get the filename,directory,line#,col#, all packag...

...pproach like this: > > Given an instruction in the a basic block, scan up and/or down the basic > block, stopping at the first llvm.dbg.stoppoint instruction. Something > like this should work: > > #include "llvm/IntrinsicInst.h" > ... > > for (...) > if (DbgStopPointInst *SP = dyn_cast<DbgStopPointInst>(Inst)) > std::cerr << "Loc: " << SP->getFileName() << ":" << SP->getLine() << > "\n"; > > If you look at IntrinsicInst, you'll see methods to get the > filename,directory...

Duncan: I'm still stymied how this whole thread ended up about shuffle vector nodes, when the original problem was my build vector patch. I'm still working on backing the build vector patch out (it isn't clean with all of the intervening commits and I have pressing management tasks which command my attention.) -scooter On Tue, Feb 24, 2009 at 12:28 AM, Duncan Sands <baldrick at

> 3. Introduce a new ShuffleVectorSDNode that only has two SDValue > operands (the two input vectors), but that also contains an array of > ints in the node (not as operands). ... > The important part of #3 is that we really want an array of ints > (using -1 for undef) for the shuffle mask, not "operands". This > eliminates the nastiness we have now were we

Hi, I would like to know how to locate an LLVM instruction in the source code, i.e. to get the line number of its corresponding source code statement. I remember in LLVM 2.4, DbgStopPointInst is designed to help this locating, but it seems deprecated in the latest LLVM. Thanks, Jingyue -- Jingyue Wu Department of Computer Science Columbia University New York, NY 10027

...struction in the a basic block, scan up and/or down the basic > > block, stopping at the first llvm.dbg.stoppoint instruction. Something > > like this should work: > > > > #include "llvm/IntrinsicInst.h" > > ... > > > > for (...) > > if (DbgStopPointInst *SP = dyn_cast<DbgStopPointInst>(Inst)) > > std::cerr << "Loc: " << SP->getFileName() << ":" << SP->getLine() << > > "\n"; > > > > If you look at IntrinsicInst, you'll see methods to get the &gt...

...ere is some sample code from SAFECode that finds the debug information associated with a CallInst (LLVM call instruction) held in the variable CI. It uses the findStopPoint() function in llvm/Analyis/DebugInfo.h: // // Get the line number and source file information for the call. // const DbgStopPointInst * StopPt = findStopPoint (CI); Value * LineNumber; Value * SourceFile; if (StopPt) { LineNumber = StopPt->getLineValue(); SourceFile = StopPt->getFileName(); } -- John T. Török Edwin wrote: > On 2009-07-09 11:17, Aaron Gray wrote: > >>>> -----Original Me...

...ere is some sample code from SAFECode that finds the debug information associated with a CallInst (LLVM call instruction) held in the variable CI. It uses the findStopPoint() function in llvm/Analyis/DebugInfo.h: // // Get the line number and source file information for the call. // const DbgStopPointInst * StopPt = findStopPoint (CI); Value * LineNumber; Value * SourceFile; if (StopPt) { LineNumber = StopPt->getLineValue SourceFile = StopPt->getFileName(); } -- John T. Hi John, What I am after is to be able to emit line number information for COFF (Common Object File Forma...

John, If you look at the stoppoint calls you'll see that you can find the line number and if you follow the compile unit argument on the call you will find the file. The byte codes that follow the call would have been generated by the code on that source line. -- Jim On Apr 8, 2006, at 5:33 AM, John Trimble wrote: > Thanks for your help. I took a look at http://llvm.org/docs/

Thanks for your help. I took a look at http://llvm.org/docs/SourceLevelDebugging.html and it seems like this doesn't give you much in the way of line number information. If you know what source line you are interested in then you can set a breakpoint, but suppose you want to know the line number in the source code for some arbitrary bytecode instruction. In my particular case, I have a pass

On Feb 13, 2010, at 7:22 AM, Jingyue Wu wrote: > I would like to know how to locate an LLVM instruction in the source > code, i.e. to get the line number of its corresponding source code > statement. I remember in LLVM 2.4, DbgStopPointInst is designed to > help this locating, but it seems deprecated in the latest LLVM. We were discussing that a few days ago: http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-February/029245.html Trevor

On 2009-07-09 11:17, Aaron Gray wrote: >>> -----Original Message----- >>> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] >>> >> On >> >>> Behalf Of Saman Aliari Zonouz >>> Sent: Thursday, July 09, 2009 11:44 AM >>> To: llvmdev at cs.uiuc.edu >>> Subject: [LLVMdev] Source file

>> -----Original Message----- >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On >> Behalf Of Saman Aliari Zonouz >> Sent: Thursday, July 09, 2009 11:44 AM >> To: llvmdev at cs.uiuc.edu >> Subject: [LLVMdev] Source file information. >> >> Hi, >> >> I am new to LLVM, and need to find the line number

...ode that finds the debug information > associated with a CallInst (LLVM call instruction) held in the variable > CI. It uses the findStopPoint() function in llvm/Analyis/DebugInfo.h: > > // > // Get the line number and source file information for the call. > // > const DbgStopPointInst * StopPt = findStopPoint (CI); > Value * LineNumber; > Value * SourceFile; > if (StopPt) { > LineNumber = StopPt->getLineValue > SourceFile = StopPt->getFileName(); > } > > -- John T. > > Hi John, > > What I am after is to be able to emit li...

Dear developers, When I try to map line numbers in source code back to LLVM basicblocks, I meet some problems: there is a source file with 1500 lines of code, but when I use BasicBlockPass to collect all DbgStopPoint instructions in this file, I can only get 500 lines of code. The source code and the collected results are both attached. Is there any way to map line numbers