search for: shankhabanerjee

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 and I couldn't...

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

...ake 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 >> I looked a...

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

Hi Duncan, Thanks for pointing out my mistake. I will reword my questions. //C code int var1; //global int a, b; foo(a, b); bar(c); generates following //LLVM IR %1 = load a; %2 = load b; call foo(%1, %2) call bar(@var1) CallInst.getOperand(1).getNameStr() on foo, returns null, but on bar returns var1. Similarly, for call void @p_ptr(i64 ptrtoint (%struct.my_struct* @abc to i64)) nounwind,

Hi, I am trying to figure out how to read arguments of a call instruction. I had few questions based on that I have the following C Code 1 #include <stdio.h> 2 3 struct my_struct 4 { 5 int a; 6 int b; 7 }; 8 9 struct my_struct abc; 10 void p_ptr ( unsigned long j) 11 { 12 printf ( "%lx \n", j ); 13 } 14 15 void struct_ptr ( struct my_struct *

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