search for: valuesymboltable

Hi all, I have a question regarding populating ValueSymbolTable of a Function. Is it that ValueSymbolTable is populated automatically whenever an alloca instruction is created using IRBuilder or do we need to explicitly populate?? If we need to populate explicitly, the insert method in ValueSymbolTable is private, so how can we do it? Currently, I am trying to...

Hello, Why are ValueSymbolTable's mutators all private? I can't seem to find a way to add a symbol to the table without using one of them. It looks like a bug to me since there is no way to use it otherwise. --Sam

...sed for though. --Sam ----- Original Message ---- > From: Chris Lattner <clattner at apple.com> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Sent: Fri, July 9, 2010 3:03:50 PM > Subject: Re: [LLVMdev] ValueSymbolTable's mutators are private? > > > On Jul 9, 2010, at 12:02 PM, Samuel Crow wrote: > > > Hello, > > > > Why are ValueSymbolTable's mutators all private? I can't seem to find a way >to > > > add a symbol to the table without using one of them...

On Jul 9, 2010, at 12:02 PM, Samuel Crow wrote: > Hello, > > Why are ValueSymbolTable's mutators all private? I can't seem to find a way to > add a symbol to the table without using one of them. It looks like a bug to me > since there is no way to use it otherwise. The mutators are things like Value::setName() -Chris

subramanyam wrote: > > Hi all, > I have a question regarding populating ValueSymbolTable of a Function. > Is it that ValueSymbolTable is populated automatically whenever an alloca > instruction is created using IRBuilder or do we need to explicitly > populate?? It's maintained by LLVM for you, by Value::setName and other methods. Nick

...Nick > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > I am getting the following error when trying to fetch the symbol table using getValueSymbolTable() /home/llvm/install/include/llvm/ADT/StringMap.h:256: void llvm::StringMap<ValueTy, AllocatorTy>::operator=(const llvm::StringMap<ValueTy, AllocatorTy>&) [with ValueTy = llvm::Value*, AllocatorTy = llvm::MallocAllocator]: Assertion `RHS.empty() && "assignment from non...

> I am getting the following error when trying to fetch the symbol table using > getValueSymbolTable() Why do you want to do this? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Anton Korobeynikov-2 wrote: > >> I am getting the following error when trying to fetch the symbol table >> using >> getValueSymbolTable() > Why do you want to do this? > > > > I want to access some of the variables created in the function. -- View this message in context: http://old.nabble.com/Using-ValueSymbolTable...-tp29461430p29469794.html Sent from the LLVM - Dev mailing list archive at Nabble.com.

...m 2.5. I initially built it with GCC 4.1.2 and it completed building. But when I run it with a simple test function, it fails with the following issue: Value still in symbol table! Type = 'i32' Name = 'a' Value still in symbol table! Type = 'i32' Name = 'b' llc: ValueSymbolTable.cpp:29: llvm::ValueSymbolTable::~ValueSymbolTable(): Assertion `vmap.empty() && "Values remain in symbol table!"' failed. I googled an found some answer that it was because the compiler I used to build llvm is not right, so I switched it to gcc 4.3 which is not on the broken...

...cate -disable-output [x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name = 'poscnt.1' [x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name = 'tmp.289' [x86_64-off-opt]: llvm-as: /ptmp/dag/llvm- project.official/llvm/tags/RELEASE_25/lib/VMCore/ValueSymbolTable.cpp:29: llvm::ValueSymbolTable::~ValueSymbolTable(): Assertion `vmap.empty() && "Values remain in symbol table!"' failed. [x86_64-off-opt]: 0 llvm-as 0x000000000056812a [x86_64-off-opt]: 1 libc.so.6 0x00002af9d6424c10 [x86_64-off-opt]: 2 libc.so.6 0x00002af9d6424b95...

...es of variables within a BasicBlock as part of a LoopPass I am trying to make copies of the variables that are in scope in the loop body like so: //Remove the existing terminator first_block->getTerminator()->eraseFromParent(); //Get the symbol table so that we know what to store ValueSymbolTable* vst = first_block->getValueSymbolTable(); IRBuilder <> builder(first_block); for (ValueSymbolTable::iterator vst_it = vst->begin(); vst_it != vst->end(); vst_it++) { AllocaInst* store_var = builder.CreateAlloca(type, 0,my_name.c_str()); builder.CreateStore(sym...

...the problem is that this modified name > cannot be demangled. > > > > That is what I am trying to fix. > > > > In similar situations gcc appends a ‘.’ before appending the > discriminating number, making “_ZL3ByePi.1” > > > > The following change in lib/IR/ValueSymbolTable.cpp seems to fix this > problem. > > > > ------------ start diff ------------------- > > @@ -54,5 +54,5 @@ void ValueSymbolTable::reinsertValue(Value* V) { > > // Trim any suffix off and append the next number. > > UniqueName.resize(BaseSize); > > -...

...of the first things we do is add a global variable named foo which is a [ 100 x i64 ]. Later we add a function void foo(...) unfortunately, when we do the getOrInsertFunction we get back void (...) * bitcast ([100 x i64]* @foo_ to void (...)*) because the symbol foo already exists in the ValueSymbolTable. Am I correct in interpreting this as a constraint that no two items in the ValueSymbolTable can have the same name, even if they're of entirely different types (in this case Function entry point and global variable) ? Is there any way, short of renaming on our end, around this? Thanks!...

...> [x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name = 'poscnt.1' > [x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name = 'tmp.289' > [x86_64-off-opt]: llvm-as: /ptmp/dag/llvm- > project.official/llvm/tags/RELEASE_25/lib/VMCore/ValueSymbolTable.cpp:29: > llvm::ValueSymbolTable::~ValueSymbolTable(): Assertion `vmap.empty() && > "Values remain in symbol table!"' failed. > [x86_64-off-opt]: 0   llvm-as   0x000000000056812a > [x86_64-off-opt]: 1   libc.so.6 0x00002af9d6424c10 > [x86_64-off-opt]: 2   libc.s...

...9; Value still in symbol table! Type = 'i32' Name = 'tmp1' Value still in symbol table! Type = 'i32' Name = 'tmp3' Value still in symbol table! Type = 'i32' Name = 'tmp3.1' Value still in symbol table! Type = 'i32' Name = 'tmp3.2' llc: ValueSymbolTable.cpp:29: llvm::ValueSymbolTable::~ValueSymbolTable(): Assertion `vmap.empty() && "Values remain in symbol table!"' failed. llc[0x89482d6] /lib/libc.so.6(abort+0x101)[0xc7a631] /lib/libc.so.6(__assert_fail+0xfb)[0xc7216b] llc[0x88e92ba] Aborted When I run lli, I get pretty much...

...nstrTypes.h" #include "llvm/IR/Instructions.h" +#include "llvm/IR/IntrinsicInst.h" #include "llvm/IR/Module.h" #include "llvm/IR/Operator.h" +#include "llvm/IR/Statepoint.h" #include "llvm/IR/ValueHandle.h" #include "llvm/IR/ValueSymbolTable.h" #include "llvm/Support/Debug.h" @@ -570,6 +572,13 @@ static bool isDereferenceablePointer(const Value *V, const DataLayout *DL, return true; } + // For gc.relocate, look through relocations + if (const IntrinsicInst *I = dyn_cast<IntrinsicInst>(V)) + if (I-&g...

...ded to it, making it “_ZL3ByePi1”. While the code is all correct, the problem is that this modified name cannot be demangled. That is what I am trying to fix. In similar situations gcc appends a ‘.’ before appending the discriminating number, making “_ZL3ByePi.1” The following change in lib/IR/ValueSymbolTable.cpp seems to fix this problem. ------------ start diff ------------------- @@ -54,5 +54,5 @@ void ValueSymbolTable::reinsertValue(Value* V) { // Trim any suffix off and append the next number. UniqueName.resize(BaseSize); - raw_svector_ostream(UniqueName) << ++LastUnique; + r...

...is emitted when the section is already created. See https://llvm.org/bugs/show_bug.cgi?id=26941 for more details and motivation. I think it would make sense to disallow global definitions with the same name as a section. Unfortunately, sections are not values, and it makes it hard to track them (ValueSymbolTable could implement value renaming in case of conflicts, but there is no direct way of knowing if the section name is currently in use or not without rescanning the module). Changing IR representation of sections just for this sounds like overkill. Another option is to allow the conflict, and make the...

...new temporary variable I have inserted an AllocaInst (...) providing the name of the temporary and desired type. But whenever I am going to insert a LoadInst for that variable I am getting segmentation fault. It is telling that llvm::Value::setName(...) fails and that has something to do with llvm::ValueSymbolTable::createValueName(...) method. What should I do to insert the local variable? Thanks and regards, Abhirup Ghosh M. Tech Department of Computer Science & Engg. IIT, Bombay email - abhirupju at gmail.com , abhirup at cse.iitb.ac.in

Hi All, I need to implement something like a variable for each basic block How to implement lookup table in LLVM , I think ValueSymbolTable is closest one but how could I do that by it -- * Rasha Salah Omar Msc Student at E-JUST Demonestrator at Faculty of Computers and Informatics Benha University* * e-mail: rasha.omar at ejust.edu.eg* P* Please consider the environment before printing this email.* -------...