Displaying 7 results from an estimated 7 matches for "llvmopaquetyp".
Did you mean:
llvmopaquetype
2008 Sep 08
3
[LLVMdev] Problems when refining type
...ause problems. I sort of feel like it probably shouldn't be
found because the opaque types should be distinct, but I also don't
really understand how it ought to work, so maybe I'm way off base.
-------------
#include "Core.h"
int main()
{
LLVMTypeRef a = LLVMPointerType(LLVMOpaqueType(), 0);
LLVMTypeHandleRef ha = LLVMCreateTypeHandle(a);
LLVMTypeRef atypes[1] = { LLVMResolveTypeHandle(ha) };
LLVMRefineType(LLVMResolveTypeHandle(ha), LLVMStructType(atypes, 1, 0));
LLVMTypeRef b = LLVMPointerType(LLVMOpaqueType(), 0); // assert here
....
}
-------------...
2008 Sep 08
0
[LLVMdev] Problems when refining type
On Mon, Sep 8, 2008 at 2:45 PM, Scott Graham <scott.llvm at h4ck3r.net> wrote:
> LLVMTypeRef a = LLVMPointerType(LLVMOpaqueType(), 0);
> LLVMTypeHandleRef ha = LLVMCreateTypeHandle(a);
> LLVMTypeRef atypes[1] = { LLVMResolveTypeHandle(ha) };
> LLVMRefineType(LLVMResolveTypeHandle(ha), LLVMStructType(atypes, 1, 0));
>
> Can anyone explain what I'm doing wrong here?
It looks like a bug; the type...
2008 Mar 04
1
[LLVMdev] [PATCH] Prefer to use *.opt ocaml executables as they are more efficient.
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
2008 Mar 04
0
[LLVMdev] [PATCH] Cleanup the c and ocaml binding documentation.
...odule *LLVMModuleRef;
>
> /**
> - * Each value in the LLVM IR has a type, an instance of [lltype].
> See the
> - * llvm::Type class.
> + * Each value in the LLVM IR has a type, an instance of
> [LLVMTypeRef]. 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],...
2008 Mar 04
1
[LLVMdev] [PATCH] Cleanup the c and ocaml binding documentation.
---
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:
2009 Aug 29
0
[LLVMdev] A create-distinct-item function with no (other) side effects
Kenneth Uildriks wrote:
> On Fri, Aug 28, 2009 at 3:47 PM, Nick Lewycky<nlewycky at google.com> wrote:
>>
>> 2009/8/28 Kenneth Uildriks <kennethuil at gmail.com>
>>> This is by design, of course, (CreateDistinctItem does not return the
>>> same value given the same caller-visible global state) but I see no
>>> way to declare a function that:
2009 Aug 29
4
[LLVMdev] A create-distinct-item function with no (other) side effects
On Fri, Aug 28, 2009 at 3:47 PM, Nick Lewycky<nlewycky at google.com> wrote:
>
>
> 2009/8/28 Kenneth Uildriks <kennethuil at gmail.com>
>>
>> This is by design, of course, (CreateDistinctItem does not return the
>> same value given the same caller-visible global state) but I see no
>> way to declare a function that:
>>
>> 1. Returns a