search for: the_nam

Displaying 5 results from an estimated 5 matches for "the_nam".

Did you mean: the_name
2009 Apr 15
0
[LLVMdev] Accessing instruction/operand names
...sion. When you see %2 in the assembly, that's an indication that the instruction's name is empty. That is, value->getName() == "". As far as I know, llvm-dis just generates numbers in order for un-named instructions. When the instruction has a name (value->getName() == "the_name"), you get %the_name instead of the number. Does that make sense? On Wed, Apr 15, 2009 at 6:20 AM, James Stanier <j.stanier at sussex.ac.uk> wrote: > > Hello everyone, > > I'm currently constructing a graph from LLVM bitcode, and I have a question > about accessing t...
2006 Jul 14
1
Samba 3.0.23 winbind use default domain = yes behaviour
Hello list, I encountered a problem in Samba 3.0.23 regarding the winbind use default domain = yes behaviour. It only works for the users an NOT anymore for the Group. So this make getent group to show NETBIOSDOMAINNAME/group which course mail squid configuration to fail. My squid configuration allowed access based on the AD groups, which are provided by Winbindd. Tested distribution: SuSE
2009 Apr 15
7
[LLVMdev] Accessing instruction/operand names
Hello everyone, I'm currently constructing a graph from LLVM bitcode, and I have a question about accessing the names of the variables shown in the .ll assembly file, assuming it's possible... For example, with %2 = load i32* %x_addr, align 4 ; <i32> [#uses=1] I can retrieve the opcodeName() from the Instruction object, which is "load". I can also access the operand
2009 Sep 28
0
[LLVMdev] Printing Function Arguments
Hi Nick, Perhaps I am confused. What is the best way to extract information from instructions ? Is it via the, say: for (User::op_iterator i = I->op_begin(), e = I->op_end(); i != e; ++i) .... I am not sure what happens next, e.g. to the variable 'i', you should know what part of the instruction this is and cast it to the necessary type. For example, I am parsing the
2009 Sep 28
4
[LLVMdev] Printing Function Arguments
ivtm wrote: > Hey Oscar, > > I want to extract information from the instruction. > > Think writing a simple interpreter. > > I already have the CallInst instance (described above in the message). > > Via ci->getOperand(1) say I can get the 'i32 8' parameter and I can get the > 'i32' and '8' separately as Nick described. > > But I