similar to: [LLVMdev] Build fails on windows with VC2008

Hi, I need to find out the line no info for each lexical block in the code being compiled with llc. The docs mention metadata format for debug info for lexical block is !3 = metadata !{ i32, ;; Tag = 11 + LLVMDebugVersion (DW_TAG_lexical_block) metadata, ;; Reference to context descriptor i32, ;; Line

I have got the latest CVS release of LLVM. And built the Win32 MS VC++ 2003 port with modifications for MS VC++ 2005. Do bear in mind the Visual Studio ports are by no means complete, and are on going. Microsoft Visual Studio 2005 Beta (codename Whidbey) can be got from Microsoft Beta program nearly for free; the cost of postage from :-

When I load my plugin into opt or llc, I get a bunch of warnings: llc: CommandLine Error: Argument 'use-unknown-locations' defined more than once! llc: CommandLine Error: Argument 'disable-debug-info-print' defined more than once! llc: CommandLine Error: Argument 'print-dbgscope' defined more than once! llc: CommandLine Error: Argument 'disable-sched-hazard'

On Thu, Jan 27, 2011 at 1:27 AM, Talin <viridia at gmail.com> wrote: > When I load my plugin into opt or llc, I get a bunch of warnings: > > llc: CommandLine Error: Argument 'use-unknown-locations' defined more than > once! > llc: CommandLine Error: Argument 'disable-debug-info-print' defined more > than once! > llc: CommandLine Error: Argument

Hmm... if I do a print() on the result of getFileName(), I get i8 * getelementptr ([9 x i8]* @.str, i32 0, i32 0) back, but if I try to dyn_cast this to GetElementPtrInst it fails (returning null), so presumably I'm seeing a GetElementPtrConstantExpr... so how can I get at that constant i8 array without casting to a GetElementPtrInst, and with GetElementPtrConstantExpr being

I get the location with : SourceManager &SM = context.getSourceManager(); int lineStart = SM.getPresumedLoc(SR->getBegin()).getLine(); int lineEnd = SM.getPresumedLoc(SR->getEnd()).getLine(); int colStart = SM.getPresumedLoc(SR->getBegin()).getColumn(); int colEnd = SM.getPresumedLoc(SR->getEnd()).getColumn(); llvm::outs() << "For:" <<

Hi! If a pass is required then it makes sense to getAnalysis<DwarfWriter>(). getAnalysisIfAvailable<>() is used for cases where a pass want to take advantage of (or fix up) info only *if* it is available. If you prepare a patch to fix getAnalysisifAvailable<>() uses (e.g. DwarfWriter requests you mention below) then I'll apply it. - Devang On Tue, Dec 8, 2009 at 11:11

Hi! After commit http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060227/032167.html : - DIE *NewType(DIE *Unit, TypeDesc *TyDesc); + DIE *DwarfWriter::NewType(CompileUnit *Unit, TypeDesc *TyDesc); and http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060227/032227.html - DIE *DwarfWriter::NewType(CompileUnit *Unit, TypeDesc *TyDesc); + DIE *DwarfWriter::NewType(DIE

Hi,   My problem definition is to collect "end line" for each scope (i.e. start and end line for a scope). I need to dump this information while emitting target code for an architecture. Though I understand that scoping details are not modeled in LLVM. Reference: http://llvm.org/docs/SourceLevelDebugging.html#format_common_lifetime   There are 2 classes I am referring, viz, DIScope and

Hi, He is referring to current SVN head. Regards, Alex On Tue, Oct 4, 2011 at 12:08 PM, Pankaj Gode <godepankaj at yahoo.com> wrote: > What do you mean by "current top of tree"? > > Pankaj > From: Eric Christopher <echristo at apple.com> > To: Pankaj Gode <godepankaj at yahoo.com> > Cc: "llvmdev at cs.uiuc.edu" <llvmdev at

Is it consistent to have a Pass instance's run method's implementation use getAnalysisIfAvailable<AnalysisType>() (vs just using getAnalysis< AnalysisType >) when that same instance's getAnalysisUsage(AnalysisUsage &au) implementation invokes au.addRequired<AnalysisType>()? For example in the implementation of SelectionDAGISel::runOnMachineFunction(...) (called

Bugs item #6972, was opened at 2006-11-29 23:47 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=6972&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 2 Submitted By: Alex Fenton (brokentoy) Assigned to: Kevin Smith (qualitycode) Summary: Wx::ListCtrl will crash if item added before insert_column called

Dear John, Actually, I was using gWidgetsRGtk2. The solution you suggest works fine. Thank you very much. Best regards. Olivier -- ____________________________________ Olivier G. Nuñez Email: onunez en iberstat.es Tel : +34 663 03 69 09 Web: http://www.iberstat.es ____________________________________ El 27/05/2009, a las 17:28, John Verzani escribió: > Dear Olivier, > > I

What do you mean by "current top of tree"?   Pankaj ________________________________ From: Eric Christopher <echristo at apple.com> To: Pankaj Gode <godepankaj at yahoo.com> Cc: "llvmdev at cs.uiuc.edu" <llvmdev at cs.uiuc.edu> Sent: Monday, October 3, 2011 10:32 PM Subject: Re: [LLVMdev] collect end line number for scope On Oct 3, 2011, at 4:36 AM,

Hi, Some random sample of VS warning: Lot of 64 bits conversions: AsmPrinter.cpp ..\..\lib\CodeGen\AsmPrinter.cpp(277) : warning C4244: 'initializing' : conversion from 'uint64_t' to 'unsigned int', possible loss of data ..\..\lib\CodeGen\AsmPrinter.cpp(614) : warning C4244: 'argument' : conversion from 'uint64_t' to 'int', possible loss of data

Sachin, On Feb 24, 2009, at 12:27 AM, Sachin.Punyani at microchip.com wrote: > Hi, > > I want to emit the debug information in assembly through assembler > directives. Also I don’t want to emit debug information in sections > (like Dwarf). Instead the debug information will be interspersed > with the assembly. However in LLVM, debug info (e.g. stoppoint) is > read

Hi, I want to emit the debug information in assembly through assembler directives. Also I don't want to emit debug information in sections (like Dwarf). Instead the debug information will be interspersed with the assembly. However in LLVM, debug info (e.g. stoppoint) is read and made part of the DAG only when DwarfWriter is registered. How can I emit the debug information in assembly

Hi, I want to emit the debug information in assembly through assembler directives. Also I don't want to emit debug information in sections (like Dwarf). Instead the debug information will be interspersed with the assembly. However in LLVM, debug info (e.g. stoppoint) is read and made part of the DAG only when DwarfWriter is registered. How can I emit the debug information in assembly

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

Hi! I want to use LLVM for my own "pet" programming language compiler as a backend. Currently it generates C code, but I am not satisfied with this approach as generating high-level C (with proper type declarations!) is horrible. So here are my questions/problems with LLVM: 1.) Are there operations that add, sub, mul integers with overflow checking? How much work would it be to add