Displaying 4 results from an estimated 4 matches for "ungetelementptr".
Did you mean:
getelementptr
2009 Jun 13
0
[LLVMdev] ML types in LLVM
...ng every distinct type its own address space and casting
back and forth between address spaces as necessary.
> Is there any way to express that a pointer is actually a pointer to an
> interior element of a type? Something like %opt_33_in_heap =
> %opt_33_with_header:1 ?
Something like an ungetelementptr? No, sorry. That would be a
pretty nice extension, though obviously unsound, of course.
> Currently when I want to read the header of an %opt_33, I cast it to a
> i32* and then use getelementptr -1. Is there a better way?
I think it depends on (1) exactly how your runtime environment lays...
2009 Jun 14
5
[LLVMdev] ML types in LLVM
...e GC
intrinsics used on them. Also I get the impression that this would be
a pretty unsafe idea. ;)
> Is there any way to express that a pointer is actually a pointer to an
> interior element of a type? Something like %opt_33_in_heap =
> %opt_33_with_header:1 ?
>
> Something like an ungetelementptr? No, sorry. That would be a
> pretty nice extension, though obviously unsound, of course.
Well, ungetelementptr could be nice, but I was hoping for something
even better: a way to refer to the whole object type (including the
header) even though my pointer doesn't point to the start of th...
2009 Jun 13
4
[LLVMdev] ML types in LLVM
Good afternoon!
I'm trying to write an LLVM codegen for a Standard ML compiler
(MLton). So far things seem to match up quite nicely, but I have hit
two sticking points. I'm hoping LLVM experts might know how to handle
these two cases better.
1: In ML we have some types that are actually one of several possible
types. Expressed in C this might be thought of as a union. The codegen
only
2009 Jun 14
0
[LLVMdev] ML types in LLVM
...Also I get the impression that this would be
> a pretty unsafe idea. ;)
>
>> Is there any way to express that a pointer is actually a pointer to an
>> interior element of a type? Something like %opt_33_in_heap =
>> %opt_33_with_header:1 ?
>>
>> Something like an ungetelementptr? No, sorry. That would be a
>> pretty nice extension, though obviously unsound, of course.
>
> Well, ungetelementptr could be nice, but I was hoping for something
> even better: a way to refer to the whole object type (including the
> header) even though my pointer doesn't...