similar to: [LLVMdev] Local variable information in scope

On Oct 12, 2011, at 3:14 AM, Pankaj Gode wrote: > Hi all, > > Using "CodeGen/LexicalScopes" pass, I could collect scope information i.e. start and end line numbers. > > I also want to collect information of variables within the scope. > > For the below example: > > int global; > int func( int t) > { > //scope 1 > { > int a;

Hi,   I want to list some additional information on this.   The variable collection I am looking at is, "variables 'declared' in scope".   1. When I traverse the MachineInstructions in the LexicalScopes ranges, and check for variables, I get variables used in this scope.      The variables listed include variables which may not have been declared in the scope. (for example

Pankaj, If you want to decorate MachineInstrs then for the end of scope you're not looking at "}" but instead you're looking at _last_ machine instruction in that scope. Now, if you want to find out start and end MachineInstrs for a lexical scope (and corresponding line numbers) then see CodeGen/LexicalScopes pass. It collects lexical scope information and maps MIs to respective

Hi,   The link and the information shared was helpful.   I will make my problem definition more clear. While I am "asm printing" target code, I also want to emit scope related information. Scope related information includes, - for each scope, start line, end line, start column, end column and - scope heirarchy. As scope is delimited by "{" and "}" (for an input

Hi Eric,  I was considering machine instructions to get scope information. And variable declaration does not correspond to machine instruction, hence the problem i.e. no scope associated with it. If 'i' is initialized in the 'if-scope' then we get 'variable i' mapped to correct scope as corresponding machine instruction is generated for this. This is not a problem as we

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, 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

Hi All,   int global; int func( int t) {    //scope 1   {      ....   } <-----   return x; }   For the above code, i want to collect endline (indicated by <---) for the scope. Can we get this information from the Dwarf Information in llvm 2.9 ?     Thanks & Regards, Pankaj -------------- next part -------------- An HTML attachment was scrubbed... URL:

Thank your reply. Pankaj. Actually, I have done it very similar to yours. But I think for my demand, it is better to implement in Front End. Maybe I will re-implement it later in clang. ---------- Forwarded message ---------- From: Pankaj Gode [via LLVM] <ml-node+s1065342n59345h22 at n5.nabble.com> Date: Mon, Jul 15, 2013 at 2:35 PM Subject: Re: Regarding scope information for variable

On Oct 3, 2011, at 4:36 AM, Pankaj Gode wrote: > For the above code, i want to collect endline (indicated by <---) for the scope. Can we get this information from the Dwarf Information in llvm 2.9 ? > I don't know about 2.9 in specific, but current top of tree will get you that information. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL:

Pankaj, On Oct 3, 2011, at 4:36 AM, Pankaj Gode wrote: > Hi All, > > int global; > int func( int t) > { > //scope 1 > { > .... > } <----- > return x; > } > > For the above code, i want to collect endline (indicated by <---) for the scope. Can we get this information from the Dwarf Information in llvm 2.9 ? > If there is no code

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

Hello everyone, In December, I had started a thread on scoped no-alias metadata in order to represent C99 'restrict' pointer information at the IR level: http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-December/056586.html At this point, we also have another important use case: preserving the existing 'noalias' attributes on pointers after inlining. My original proposal was

----- Original Message ----- > From: "Raul Silvera" <rsilvera at google.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "Chandler Carruth" <chandlerc at google.com>, "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Friday, November 14, 2014 10:34:39 AM > Subject: Re: [LLVMdev] Upcoming

Hello again, When I had originally discussed this proposal, it was thought that we would not have to worry about control dependencies on the noalias metadata because such dependencies could only present a problem when loads or stores are merged (RAUW is called), and transformations should drop metadata when that happens. Now I'm worried that this is not true. Here's a simple example:

Hi Eric,   Thanks for patch information. I have checked the patch with my code and I see that it works. But when I extract the variable and check the metadata information to retrieve the scope information, I do not get exact scope, after optimization. As you said that this is a work in progress, so can we expect full version on this in llvm3.3 release ?   Regards, Pankaj  

Dear All, I am following a flow to generate object files(.o) from input (.s assembly) files. The input .s is given to AsmParser, which creates MCInst after matching instruction opcode. These MCInst are converted to MCStream and then finally emitting to an object file using Target Code Emitter. I am considering whether hazard recognition can be done on the list of MCInst, which I get after

Hi All,   Due to 'LowerDbgDeclare' call ( as part of 'instruction combining' optimization), a local variable gets declared and initialized inside the basic blocks it is used in. Is there anyway I can avoid this ?   This is with reference with my previous question. http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061644.html     Regards, Pankaj -------------- next part

Hi All,   While collecting type information for "anonymous types", I had below observation.   For the example with anonymous types, given below struct test {   struct {     union {       Char a[4];     };   };   struct {     int b;     char c;   }; };   LLVM 2.6 defines the types as %struct.anon1 = type { %union.anon0} %struct.anon2 = type { i32, i8} %struct.test = type {

There was a patch committed the other day that should, at least, work around some of the behavior you describe. Optimized debug info is an area that's being worked on in ToT and previous releases are particularly bad. I'd use that. -eric On Mon, Apr 29, 2013 at 7:02 AM, Pankaj Gode <godepankaj at yahoo.com> wrote: > Hi All, > > Due to 'LowerDbgDeclare' call ( as