search for: abstracttyp

Chris, good to see the AbstractType stuff vaporize, but I still have a question, the Type system seems to have a "shadow type" system, every user Type created also has a corresponding XYZValType, is the "shadow type" system still retained ? It's purpose seems(?) to be for factoring the "unique-i...

Hi (Gordon). There appears to be two wrapper functions for DerivedType::refineAbstractTypeTo() in llvm-c (Core.h, Core.cpp): void LLVMRefineAbstractType(LLVMTypeRef AbstractType, LLVMTypeRef ConcreteType){ DerivedType *Ty = unwrap<DerivedType>(AbstractType); Ty->refineAbstractTypeTo(unwrap(ConcreteType)); } void LLVMRefineType(LLVMTypeRef AbstractTy, LLVMTypeRef ConcreteT...

Hi, Consider ConstantUniqueMap::getOrCreate() (in lib/VMCore/ConstantsContext.h): /// getOrCreate - Return the specified constant from the map, creating it if /// necessary. ConstantClass *getOrCreate(const TypeClass *Ty, ValRefType V) { MapKey Lookup(Ty, V); ConstantClass* Result = 0; ... For array (or struct or vector) constants, typically: ValType = vector<Constant*>

...nker needs to resolve types correctly. 2. The bitcode reader needs support for LLVM 2.9 bitcode files. 3. Clang/dragonegg need to adapt to the new API (help appreciated!) 4. LangRef and Programmer's manual need to be updated. Once that lands, the constant uniquing is greatly simplified because AbstractType stuff all vaporizes. When the branch lands, the constant uniquing maps should all be replaced with folding sets. -Chris

I noticed that the ocaml compilation isn't using the .opt executables if they're available. We might gain a slight optimization in ocaml compile time by optionally using them with this patch. --- autoconf/configure.ac | 18 +++++ configure | 195 ++++++++++++++++++++++++++++++++++++++++++------ 2 files changed, 188 insertions(+), 25 deletions(-) -------------- next part

...VMTypeRef]. See the > + * [llvm::Type] class. > */ > typedef struct LLVMOpaqueType *LLVMTypeRef; > > /** > - * When building recursive types using [refine_type], [lltype] > values may become > - * invalid; use [lltypehandle] to resolve this problem. See the > - * llvm::AbstractTypeHolder] class. > + * When building recursive types using [LLVMRefineType], > [LLVMTypeRef] values may become > + * invalid; use [LLVMTypeHandleRef] to resolve this problem. See the > + * [llvm::AbstractTypeHolder] class. > */ > typedef struct LLVMOpaqueTypeHandle *LLVMTypeHandl...

--- bindings/ocaml/llvm/llvm.ml | 2 +- bindings/ocaml/llvm/llvm.mli | 2 +- bindings/ocaml/llvm/llvm_ocaml.c | 2 +- include/llvm-c/Core.h | 32 +++++++++++++++++++------------- 4 files changed, 22 insertions(+), 16 deletions(-) -------------- next part -------------- A non-text attachment was scrubbed... Name: 316a84e85ed2363551149e65a227c8e7c8192624.diff Type: