search for: shankha

Hi Devang, Is there any particular reason as to why debug info support for tls hasn't been implemented. Is the feature in pipeline ? How hard is it to implement ? On Wed, Oct 13, 2010 at 4:12 PM, Devang Patel <dpatel at apple.com> wrote: > > On Oct 13, 2010, at 10:09 AM, shankha wrote: > > Hi Devang, > > On Wed, Oct 13, 2010 at 12:44 PM, Devang Patel <dpatel at apple.com> wrote: > > In your example, you do not need to update debug info for @global_var at the > moment. We are not identifying tls in debug info yet. > > Does that mean I will n...

...: > In your example, you do not need to update debug info for @global_var at the moment. We are not identifying tls in debug info yet. Does that mean I will not be able to debug applications which use tls through gdb if they are build with gcc-lllvm or clang. > On Oct 13, 2010, at 8:30 AM, shankha wrote: > >> I do not face any issues debugging my test case. But while debugging >> my application >> through gdb I cannot make sense of the call stack. I do not see the >> function names in >> the call stack (with or without insertion of additional function calls &...

...If I convert global variables to thread-local variables or vice versa at the IR stage do I have to take care of the debug metadata. I looked at the IR generated and I couldn't find any difference between the debug metadata generated for global variables and thread-local variables. -- Thanks Shankha

...b I cannot make sense of the call stack. I do not see the function names in the call stack (with or without insertion of additional function calls or local variables). On Wed, Oct 13, 2010 at 10:35 AM, Devang Patel <dpatel at apple.com> wrote: > > > > On Oct 12, 2010, at 4:28 PM, shankha <shankhabanerjee at gmail.com> wrote: > >> Hi, >> If I convert global variables to thread-local variables or vice versa >> at the IR stage do I have to take care of the debug metadata. > > If you provide an small concrete example then it would help, > > Devang...

Shankha, AFAIK, nobody is actively working on debug info for TLS at the moment. On Oct 13, 2010, at 3:19 PM, shankha wrote: > Hi Devang, > Is there any particular reason as to why debug info support for tls > hasn't been implemented. > Is the feature in pipeline ? How hard is it to implem...

On Oct 12, 2010, at 4:28 PM, shankha <shankhabanerjee at gmail.com> wrote: > Hi, > If I convert global variables to thread-local variables or vice versa > at the IR stage do I have to take care of the debug metadata. If you provide an small concrete example then it would help, Devang > I looked at the IR generated...

On Oct 13, 2010, at 10:09 AM, shankha wrote: > Hi Devang, > > On Wed, Oct 13, 2010 at 12:44 PM, Devang Patel <dpatel at apple.com> wrote: >> In your example, you do not need to update debug info for @global_var at the moment. We are not identifying tls in debug info yet. > > Does that mean I will not be ab...

In your example, you do not need to update debug info for @global_var at the moment. We are not identifying tls in debug info yet. On Oct 13, 2010, at 8:30 AM, shankha wrote: > I do not face any issues debugging my test case. But while debugging > my application > through gdb I cannot make sense of the call stack. I do not see the > function names in > the call stack (with or without insertion of additional function calls > or local variables)....

...4> [#uses=1] call void @p_ptr(i64 %stack_abc1) nounwind, !dbg !33 Q.2 stack_abc1 is a alias for the operation performed by the ptrtoint instruction. Which fields from the instruction class will help me read if I may say the "output" of the instruction ? Thanks Shankha Banerjee

Hi, Are there any options that can be used with llvm-dis to generate LLVM assembly along with source code if the original byte code had been built with -g. e.g. objdump -D -d -S -l executable gives you the source code listing along with the assembly. -- Thanks Shankha

Hi Shankha, > 24 p_ptr ((unsigned long)&abc); > call void @p_ptr(i64 ptrtoint (%struct.my_struct* @abc to i64)) > nounwind, !dbg !31 > > Q.1 At line no 24 I try to read the address of global variable abc. > The address is type casted > from struct * to int * fo...

...ruct* @abc to i64)) nounwind, !dbg !52 I think by the call CI->getArgOperand(0) you mean CI->getOperand(0). That doesn't return the ptrtoint constant expression. The CI instruction has shows two operands. The first operand is the function name. The second operand prints NULL. thank you, Shankha Banerjee