search for: global_var

...by running the following code: bool erased = true; while (erased) { erased = false; for (Module::global_iterator gi = llvm_module.global_begin(), ge = llvm_module.global_end(); gi != ge; ++gi) { GlobalVariable *global_var = dyn_cast<GlobalVariable>(gi); if (global_var->use_empty()) { log->Printf("Did remove %s", PrintValue(global_var).c_str()); global_var->eraseFromParent(); erased =...

Hi Ben, That did help. I continue to notice the virtual register in the program. I use LLVM 3.4. The program i am looking at is a very simple one. Listed below int global_var; int *global_ptr; int32_t main(int32_t argc, char ** argv){ int p = 10; int k = 20; int *pp; char *c_pp; pp = &k; global_ptr = pp; pp = &p; global_ptr = &global_var; return 0; } BR/Nizam From: "Benjamin Kramer" <benny.kra at gmail.com> To: nizam...

...} %derived = type { %base1, %base2, long } void myProc(base2 obj) { } Now if you use get elementptr to obtain "base2" member of "derived" to pass it to myProc, then you're basically passing a different pointer, breaking instance identity among other things: public Derived global_var = new ....; main() { myProc(d); } void myProc(base2 obj) { boolean b = (global_var == obj); // this would be false! Derived alias = (Derived) obj; // this would break too btw } So what am i missing ? maybe to deal with multiple ereditation one need some more "manadgement" code ?...

...gt; void myProc(base2 obj) > { > } > > Now if you use get elementptr to obtain "base2" member of "derived" to > pass it to myProc, then you're basically passing a different pointer, > breaking instance identity among other things: > > public Derived global_var = new ....; > main() > { > myProc(d); > } > > void myProc(base2 obj) > { > boolean b = (global_var == obj); // this would be false! > > Derived alias = (Derived) obj; // this would break too btw > } > > So what am i missing ? maybe to deal with multi...

Here's the IR I'm trying to compile for my backend, a 16-bit CPU: ; ModuleID = 'foo.c' source_filename = "foo.c" target datalayout = "E-m:e-p16:16:16-i1:16:16-i8:16:16-i16:16:16-i32:16:16-i64:16:16-S16-n16" target triple = "tms9900" @global_var = common global i16 0, align 2 ; Function Attrs: noinline nounwind optnone define signext i16 @dothis(i16 signext %a) #0 { entry: %a.addr = alloca i16, align 2 store i16 %a, i16* %a.addr, align 2 %0 = load i16, i16* @global_var, align 2 %1 = load i16, i16* %a.addr, align 2 %add = add nsw...

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 wrote: > >> I do not face any issues debugging my test case...

...fields: "0\00clang 3.6\00...", >> operands: { metadata !8, ... }) >> >> !7 = metadata !GenericDebugMDNode(tag: DW_TAG_variable, >> fields: "global_var\00...", >> operands: { metadata !8, ... }, >> handle: i32* @global_var) >> >> This syntax pulls the tag out of the current header-string, calls >> the rest of the header "...

...DW_TAG_compile_unit, fields: "0\00clang 3.6\00...", operands: { metadata !8, ... }) !7 = metadata !GenericDebugMDNode(tag: DW_TAG_variable, fields: "global_var\00...", operands: { metadata !8, ... }, handle: i32* @global_var) This syntax pulls the tag out of the current header-string, calls the rest of the header "fields", and includes the metadata...

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

Hi, I'm writing a Scheme compiler in C++ with the LLVM library. The dynamic type system is hard to tackle with direct LLVM from the C++ lib, so I'd like to throw the work off into a C support library I could link the compiled Scheme with. How can I generate code that depends on/calls external symbols? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, is there a opt pass that replaces the SSA virtual registers to stack-variables? I want to eliminate the SSA virtual register from my IR. Kindly suggest BR/Nizam -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140201/bdc3909a/attachment.html>

If I edit the value of a global variable in my dialplan, could there be a risk of collision between calls? More in details: could a global var be used to build a counter that will be incremented by every call that passes. I think when 2 calls come in almost sumiltaneously, they could both be incrementing and saving the same value... which is bad! Anybody knows how asterisk handles this? K

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 able to debug applications which use tls > through gdb if they are build with gcc-lllvm or clang. It should not impact call stack info. > >> On Oct 13, 2010, at 8:30 AM, shankha wrote...

Hi Devang, I convert all global variables in a file to thread local at the IR level. i.e. compile example_llvm.c to IR example_llvm.ll and change global variables to thread-local variables. I also insert a function call just before access of the global(now thread-local) variable. I also insert a local variable in main. Does these operations in any way effect the debug metadata ? I do not face

...fields: "0\00clang 3.6\00...", > >> operands: { metadata !8, ... > }) > >> > >> !7 = metadata !GenericDebugMDNode(tag: DW_TAG_variable, > >> fields: "global_var\00...", > >> operands: { metadata !8, ... > }, > >> handle: i32* @global_var) > >> > >> This syntax pulls the tag out of the current header-string, calls > >>...

...nto mailbox 'INBOX' =============================== Output of 'sieved /home/tomhendr/.default.svbin =============================== * Required extensions: 0: include (16) 1: fileinto (5) Panic: file ext-include-variables.c: line 133 (ext_include_variables_dump): assertion failed: (global_vars != NULL) Error: Raw backtrace: sieved [0xa7fbfe10] -> sieved(default_fatal_handler+0x57) [0xa7fbfe97] -> sieved [0xa7fc006e] -> sieved [0xa7f7384c] -> sieved(ext_include_binary_dump+0x48) [0xa7f531c8] -> sieved(sieve_binary_dumper_run+0x119) [0xa7f671a9] -> sieved(sieve_dump+0x42...

...t; fields: "0\00clang 3.6\00...", > operands: { metadata !8, ... }) > > !7 = metadata !GenericDebugMDNode(tag: DW_TAG_variable, > fields: "global_var\00...", > operands: { metadata !8, ... }, > handle: i32* @global_var) > > This syntax pulls the tag out of the current header-string, calls > the rest of the header "fields", an...

I have looked at matt's asterisk gui client at sourceforge. I am not a programmer by trade. The documentation there seems to be a bit lacking. Has anyone have the experience in installing the gui client and may perhaps have a how-to document available for sharing. -- David Kwok Tel: 612 99292086 ext 1002 Iaxtel/FWD # 17001813482 ext 1002 -------------- next part -------------- A non-text

> Hi! i'm tring to figure out how classes and dependencies > can be mapped to llvm. > [snip] > how do i encode a function that takes "base" type > so that it also takes "derived" ? You'll notice that your function doesn't take an object of type base, but a pointer to it. This is important - in a language such as LLVM where actual structures can be

Hi! i'm tring to figure out how classes and dependencies can be mapped to llvm. I've read on docs that nesting can be used: class base { int Y; }; class derived : base { short Z; }; becomes: %base = type { int } %derived = type { %base, short } That's ok, but now the question is: how do i encode a function that takes "base" type so that it also takes "derived"