Displaying 6 results from an estimated 6 matches for "fieldval".
Did you mean:
field_val
2006 May 24
7
Using inline editor without requiring a URL
Hi,
I was wondering if anyone has implemented the inplace editor without the
need for the URL. I have tried this but run into a problem in that the
''saving...'' text in shown for ever and the label is no longer editable.
Can I also confirm that my idea of the callback function is something that
runs before the value is passed to the URL (if you were to use one). What
might be
2004 Jul 21
2
[LLVMdev] GC questions.
...dPtr;
> > }
>
> Hm, but doesn't FieldPtr need to be calculated target-specific in those
> cases?
For the field pointer, one could use the getelementptr instruction:
%pairty = { sbyte, sbyte, int* }
%pairPtr = ...
%fieldptr = getelementptr %pairty* %pairPtr, int 0, uint 2
FieldVal = llvm.gc_read(pairptr, fieldptr)
Because of the getelementptr instruction is used, we don't have the
explicit offset encoded into the bytecode file. The other advantage of
this is that when the gc_read/write intrinsics are lowered to load/stores,
the resultant LLVM code will be much simpler....
2004 Jul 21
0
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Chris Lattner wrote:
> On Wed, 21 Jul 2004, Tobias Nurmiranta wrote:
>
> This will work, but it would be better to take two pointers in instead of
> a pointer and offset. This allows the front-end to emit target-generic
> code instead of target-specific code (where it would have to know the
> offset to the field). To be more specific, llvm_gc_read should
2004 Jul 21
2
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Tobias Nurmiranta wrote:
> [1] I'm kind of newbie of cvs, but I did:
> "cvs -z3 -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm diff llvm > gcpatch"
That patch is well formed. You did exactly the right thing. :)
> Ok, a patch[1] is attached. I didn't care to coerce the offset, since I
> assume that it is an uint, but maybe I should?
2004 Jul 21
0
[LLVMdev] GC questions.
...#39;t FieldPtr need to be calculated target-specific in those
> > cases?
>
> For the field pointer, one could use the getelementptr instruction:
>
> %pairty = { sbyte, sbyte, int* }
>
> %pairPtr = ...
> %fieldptr = getelementptr %pairty* %pairPtr, int 0, uint 2
> FieldVal = llvm.gc_read(pairptr, fieldptr)
>
> Because of the getelementptr instruction is used, we don't have the
> explicit offset encoded into the bytecode file. The other advantage of
> this is that when the gc_read/write intrinsics are lowered to load/stores,
> the resultant LLVM co...
2004 Jul 22
2
[LLVMdev] GC questions.
...pecific in those
> > > cases?
> >
> > For the field pointer, one could use the getelementptr instruction:
> >
> > %pairty = { sbyte, sbyte, int* }
> >
> > %pairPtr = ...
> > %fieldptr = getelementptr %pairty* %pairPtr, int 0, uint 2
> > FieldVal = llvm.gc_read(pairptr, fieldptr)
> >
> > Because of the getelementptr instruction is used, we don't have the
> > explicit offset encoded into the bytecode file. The other advantage of
> > this is that when the gc_read/write intrinsics are lowered to load/stores,
> &...