similar to: [LLVMdev] Remove debug info from the byte code?

Hi Zheng, > Is there any easy way to remove the debug info from the LLVM byte code > once I have collected all the debug info I needed? It is because the > debug info seems to slow down the program significantly. I may be able > to go through each basic block and delete the debug info in my pass. > But, is there any elegant way to do it? the opt tool has an option called

Can I do this in my own pass module? Because the string is actually depended on the type of a value object. On 8 April 2010 20:29, Eli Friedman <eli.friedman at gmail.com> wrote: > On Thu, Apr 8, 2010 at 12:18 PM, Zheng Wang <jason.wangz at gmail.com> wrote: >> Hiya, >> >> I want to declare a constant global variable as: >> >> @.str = private constant

Thanks Edwin. I found DebugInfo.cpp may be useful. Could you tell me which function I should call inorder to know the source file name and the line number for a particular instruction? Cheers, Zheng 2010/5/18 Török Edwin <edwintorok at gmail.com>: > On 05/18/2010 01:26 PM, Zheng Wang wrote: >> Hello, >> >> Could I get some debug info at the byte code level? I am

Hiya, I want to declare a constant global variable as: @.str = private constant [4 x i8] c"%f\0A\00", align 1 ; <[4 x i8]*> [#uses=1] I guess I should firstly declare an arrayType object, then declare a GlobalVariable object. I have two problems: 1. What element type I should set for the arrayType? 2. How to set the constant value as :c"%f\0A\00" Cheers, Zheng

On Thu, Nov 21, 2013 at 11:45 AM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Thu, Nov 21, 2013 at 11:26 AM, David Blaikie <dblaikie at gmail.com>wrote: > >> >> >> >> On Thu, Nov 21, 2013 at 11:06 AM, Manman Ren <manman.ren at gmail.com>wrote: >> >>> >>> >>> >>> On Thu, Nov 21, 2013 at

On Thu, Nov 21, 2013 at 4:17 PM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Thu, Nov 21, 2013 at 12:01 PM, David Blaikie <dblaikie at gmail.com>wrote: > >> >> >> >> On Thu, Nov 21, 2013 at 11:45 AM, Manman Ren <manman.ren at gmail.com>wrote: >> >>> >>> >>> >>> On Thu, Nov 21, 2013 at

On Thu, Nov 21, 2013 at 12:01 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Thu, Nov 21, 2013 at 11:45 AM, Manman Ren <manman.ren at gmail.com> wrote: > >> >> >> >> On Thu, Nov 21, 2013 at 11:26 AM, David Blaikie <dblaikie at gmail.com>wrote: >> >>> >>> >>> >>> On Thu, Nov 21, 2013 at

On Thu, Apr 8, 2010 at 12:18 PM, Zheng Wang <jason.wangz at gmail.com> wrote: > Hiya, > > I want to declare a constant global variable as: > > @.str = private constant [4 x i8] c"%f\0A\00", align 1 ; <[4 x i8]*> [#uses=1] > > I guess I should firstly declare an arrayType object, then declare a > GlobalVariable object. > > I have two problems:

On Fri, Nov 22, 2013 at 9:08 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Thu, Nov 21, 2013 at 4:17 PM, Manman Ren <manman.ren at gmail.com> wrote: >> >> >> >> >> On Thu, Nov 21, 2013 at 12:01 PM, David Blaikie <dblaikie at gmail.com> >> wrote: >>> >>> >>> >>> >>> On Thu,

Devang Patel <devang.patel <at> gmail.com> writes: > > 2010/5/18 Zheng Wang <jason.wangz <at> gmail.com>: > > > > I found DebugInfo.cpp may be useful. Could you tell me which function > > I should call inorder to know the source file name and the line number > > for a particular instruction? > > > > See

On Fri, Nov 22, 2013 at 9:54 AM, Eric Christopher <echristo at gmail.com>wrote: > On Fri, Nov 22, 2013 at 9:08 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > > > > > On Thu, Nov 21, 2013 at 4:17 PM, Manman Ren <manman.ren at gmail.com> > wrote: > >> > >> > >> > >> > >> On Thu, Nov 21, 2013 at

2010/5/18 Zheng Wang <jason.wangz at gmail.com>: > > I found DebugInfo.cpp may be useful. Could you tell me which function > I should call inorder to know the source file name and the line number > for a particular instruction? > See http://llvm.org/docs/SourceLevelDebugging.html#ccxx_frontend At the end of "C/C++ source file information" section, there is a small

This set of patches add support for debug info metadata version and debug info metadata will be dropped if a loaded bit code has no version or an outdated version. 195494: Debug Info: add a constant for debug info version number. 195495: Debug Info: add a "Debug Info Version" module flag to output the current debug info version number. 195504: Debug Info: update testing cases to specify

Final review is done. Feel free to merge :) Thanks for the wait. -eric On Tue, Dec 3, 2013 at 1:27 PM, Eric Christopher <echristo at gmail.com> wrote: > I request that we hold off until the final review is done. > > -eric > > On Tue, Dec 3, 2013 at 12:06 PM, Manman Ren <manman.ren at gmail.com> wrote: >> >> This set of patches add support for debug info

Zheng Wang wrote: > Hiya, > > I want to know what's the type of the operand (value) along with the > store instruction. For example, the following instruction store the > content in an integer type pointer scevgep99.1 to the address another > integer pointer points to. > > *"store i8* %scevgep99.1, i8** %scevgep92.1, align 4"* > > It seems there is no

Hello, Could I get some debug info at the byte code level? I am writing a passer and if will be nice if I can know which line in the source an instruction (or value) corresponds to. I found a document online: http://llvm.org/docs/SourceLevelDebugging.html, but I can't find an example of doing it at the byte code level. Cheers, Zheng

Hiya, I want to know what's the type of the operand (value) along with the store instruction. For example, the following instruction store the content in an integer type pointer scevgep99.1 to the address another integer pointer points to. *"store i8* %scevgep99.1, i8** %scevgep92.1, align 4"* It seems there is no APIs in StoreInst can do this. Is there any way to figure the type

Hi Eli, Could you tell me how to extract the variable name? The reason I want to do it at the IR level is because I have more information at this stage, such as, constant propagation and back edges. Cheers, Zheng On 5 April 2010 21:51, Eli Friedman <eli.friedman at gmail.com> wrote: > On Mon, Apr 5, 2010 at 1:19 PM, Zheng Wang <jason.wangz at gmail.com> wrote: >> Hello,

Thanks a lot for your guys' help!!! I guess once I am able to get *V* (which probably is a pointer to a Value object), then, I can instrument some code at the IR level to dump V. As long as I maintain V at this pass stage, I should be able to dump the loop trip count. This is true, isn't it? Basically, what I am going to do is to add a function call before the loop body, such as:

On 05/18/2010 01:26 PM, Zheng Wang wrote: > Hello, > > Could I get some debug info at the byte code level? I am writing a > passer and if will be nice if I can know which line in the source an > instruction (or value) corresponds to. > > I found a document online: > http://llvm.org/docs/SourceLevelDebugging.html, but I can't find an > example of doing it at the