search for: endlines

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:

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

What happened with this? Is there something for review in Phabricator? Or was this put-on-hold/forgotten? I also have some users that complain that some gdb test suite tests don't work with LLVM due to missing debug info regarding ending brace. So gettint the location for the "endLine" field of DISubprogram etc should at least be a step in the right direction, and if someone already

I added one attribute named EndLine in LLVM IR before. LLVM's part is not hard, but will modify many places in Clang. I success for it, you can try this way. At 2018-04-12 16:53:21, "Björn Pettersson A" <bjorn.a.pettersson at ericsson.com> wrote: >What happened with this? Is there something for review in Phabricator? Or was this put-on-hold/forgotten? > >I also have

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

On 03/08/17 16:21, Robinson, Paul via llvm-dev wrote: > >> >> I have implemented this exact behavior in an out of tree LLVM fork I >> maintain, where one of my users needed this behavior, and it seems to >> work well. What we have done is extend the definition of DISubprogram to >> contain a new field "endLine" which holds the line number of the closing

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

Simon, I also think of the way you did. :-) And from my initial investigation, clang should also has some work(i.e. provide the end location for the "endLine" field of DISubprogram), right? BTW, Simon, your fork of LLVM is open source or not? If open source, could you give the address of it?  Thanks < Simon Cook via llvm-dev> 在 2017-08-04 00:10:59 写道: On 03/08/17 16:21,

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, On 12/04/2018 15:35, Frozen via llvm-dev wrote: > I added one attribute named EndLine in LLVM IR before. LLVM's part is > not hard, but will modify many places in Clang. I success for it, you > can try this way. > For loops, we use a range to keep track of the start and end of the loop for remarks: http://llvm.org/doxygen/classllvm_1_1Loop_1_1LocRange.html Maybe it would

We''re using Vpim to parse iCal and vCard files, and so far it''s been great. However, when we were parsing some iCal files we noticed that all the endlines in the description section were disappearing. I start peering through the source code and find (in the Field#to_text method that is being called): # The value as text. Text can have escaped newlines, commas, and escape # characters, this method will strip them, if present. Is there some reason th...

Hi folks, I just tried to build LLVM on FreeBSD/arm. It looks like libSystem doesn't build and requires the following hack: --- lib/System/Memory.cpp +++ lib/System/Memory.cpp @@ -61,7 +61,7 @@ for (intptr_t Line = StartLine; Line < EndLine; Line += LineSize) asm volatile("icbi 0, %0" : : "r"(Line)); asm volatile("isync"); -# elif defined(__arm__)

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:

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

I have implemented this exact behavior in an out of tree LLVM fork I maintain, where one of my users needed this behavior, and it seems to work well. What we have done is extend the definition of DISubprogram to contain a new field "endLine" which holds the line number of the closing brace. A pass late in our backend uses this information to set the DebugLoc of return instructions in our

I am reading into Java dput output for a matrix, more specifically for a file backed big-matrix. I basically need to lift dimnames for a matrix from dput output. It's no big deal, but the code is very 'hackish' due to the need to get rid of quotes, endlines, parenthesis, etc. I was wondering if i could manipulate to an extent dput output with some options that define it, for example, get rid of quoting each element in matirx dimnames somehow. Another great thing wiould be to make dput dump rownames and colnames on two separate lines, but i don't...

I really wouldn't be sure this is the right direction to go anyway - as pointed out, there coudl be a return of a constant which would be a single instruction & it would make more sense to me to attribute that to the line where "return" is written, than where the closing brace is. I think this is, for my money, a legitimate difference in implementations between GCC and Clang -

Hi all, When you genetate code on PowerPC you need to explicitly invalidate the instruction cache to force the processor to reread it. In LLVM there is code to do this for function stubs on Macintosh, but not for other platforms and not for JITted code generally. The attached patch adds support for GNU platforms, but I can't figure out a nice way to call it for all generated code. Can

Hi, I have a strange problem with sieve. After upgrading to 2.2.13 sieve seems to break the mailbody during automatic redirection. I have the following configuration. - User A sends mail to User B. - User B has an automatic redirect to User C - User C geht the mailbody broken I did some debugging. This is a part of the mailbody which i grabbed from the mailqueue before the mail gets

Remembering a discussion as to why we do this from a few years ago: (*makes note to start writing design decisions this way down somewhere*) I was in favor of the current method for a few reasons: a) ensuring that it would "always happen" that we had either a unified return block or a well propagated location onto return instructions seemed like it would be difficult to maintain and