search for: gettypenam

Displaying 8 results from an estimated 8 matches for "gettypenam".

Did you mean: gettypenum
2015 Apr 15
2
[LLVMdev] where is type symbol table now
Hello, I found some source code using llvm 2.5 that has a call to Module::getTypeName(Type*), which I can't find it anymore in llvm newer than 3.3, so how can I get the name of a type(e.g a user-defined structure) if we have Type* of that ? Besides, I checked that old llvm maintains a TypeSymbolTable that enabled type name look-up, so what's the replacement and mechanism o...
2009 Nov 25
0
[LLVMdev] JVM Backend
...c? It will be nice if this library be somehow integrated into LLVM as well. The current big question is: how you're planning to deal with arbitrary precision stuff which might come from LLVM IR. Currently all the things seems to behave different in case of receiving e.g. i31: - functions like getTypeName() return some junk (the case Type::IntegerTypeID just falls through to Type::FloatTyID) - other functions just assert -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
2009 Nov 24
2
[LLVMdev] JVM Backend
Hi, I've written a backend for LLVM that allows LLVM IR to be transformed to a Java/JVM class file (llvm-jvm.patch.gz attached). Indirect function calls don't work yet, and there's probably some minor bugs in it, but it works well for the test cases that I've run through it. Also, several instructions are emulated by method calls due to deficiencies in the JVM instruction set
2009 Nov 26
2
[LLVMdev] JVM Backend
...> arbitrary precision stuff which might come from LLVM IR. I should be able to implement that. Would arbitrary precision support be required for the initial commit of the backend? > Currently all > the things seems to behave different in case of receiving e.g. i31: > - functions like getTypeName() return some junk (the case > Type::IntegerTypeID just falls through to Type::FloatTyID) getBitWidth raises an assertion before this can happen. -- David Roberts http://da.vidr.cc/ On Wed, Nov 25, 2009 at 21:03, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hello, David...
2008 Nov 15
1
[LLVMdev] How to use EE->runFunction for a function with StructRet set?
...llov"); // XXX Is all of this the right way? const Type* paramType = F->getFunctionType()->getParamType(0); // pointer to struct const Type* structRetType = dynamic_cast<const PointerType*>(paramType)->getTypeAtIndex((unsigned)0); const std::string structRetName(M->getTypeName(structRetType)); if (structRetName != "struct.std::string") return 1; // Get object size uint64_t size = EE->getTargetData()->getABITypeSize(structRetType); // Make room on stack void* p = alloca(size); // Create parameter list std::vector<GenericValue> p...
2007 Jul 03
0
[LLVMdev] Solaris 9 compilation
...vModopt(unsigned int)': /home/ggreif/llvm/lib/Target/MSIL/MSILWriter.cpp:261: warning: control reaches end of non-void function llvm[3]: Compiling ValueEnumerator.cpp for Release build /home/ggreif/llvm/lib/Target/MSIL/MSILWriter.cpp: In member function `std::string <unnamed>::MSILWriter::getTypeName(const llvm::Type*, bool, bool)': /home/ggreif/llvm/lib/Target/MSIL/MSILWriter.cpp:333: warning: control reaches end of non-void function 8) /home/ggreif/llvm/lib/Target/ARM/ARMInstrInfo.cpp: In function `unsigned int llvm::ARM::GetInstSize(llvm::MachineInstr*)': /home/ggreif/llvm/lib/Tar...
2012 Nov 06
2
[LLVMdev] [PATCH] basic reading reloc visitor for x86_64 ELF
...reloc_i->getType(Type); + + RelocVisitor V(Obj->getFileFormatName()); + // The section address is always 0 for debug sections. + RelocToApply R(V.visit(Type, *reloc_i)); + if (V.error()) { + SmallString<32> Name; + error_code ec(reloc_i->getTypeName(Name)); + if (ec) { + errs() << "Aaaaaa! Nameless relocation! Aaaaaa!\n"; + } + errs() << "error: failed to compute relocation: " + << Name << "\n"; + continue; + } + +...
2012 Nov 06
0
[LLVMdev] [PATCH] basic reading reloc visitor for x86_64 ELF
On Mon, Nov 5, 2012 at 5:17 PM, Eric Christopher <echristo at gmail.com> wrote: > For llvm-dwarfdump we need to handle relocations inside the debug info > sections in order to successfully dump the dwarf info including strings. > Nick sent out a partial patch that did this not too long ago and I've taken > it and gone in a bit of a different direction, but kept the same basic