search for: setelementdoubl

...linkage? >> > > Probably an intrinsic. The trick is making it general purpose, not > language specific. > > I'm not sure actually how can I do that language specific ;). OK currently only Java does that (from what I know), but intrinsics like getElementDouble or setElementDouble do look general purpose. Unless, I'm too Java-minded? >> 2) At which point in LLVM do we know we won't have any optimization, so >> that the field operation is next to the stub call? >> > > You'll probably want to do this late in the code generator. >...

On Wed, 7 Nov 2007, Nicolas Geoffray wrote: > I'm not sure actually how can I do that language specific ;). OK > currently only Java does that (from what I know), but intrinsics like > getElementDouble or setElementDouble do look general purpose. Unless, > I'm too Java-minded? Focus on the mechanism behind what you want to do, not on what you want to do itself :). Think about a way to separate what you want to accomplish from how it gets done. >> You'll probably want to do this late in the cod...

On Wed, 7 Nov 2007, Nicolas Geoffray wrote: > Thanks BGB, but at this point I can handle it ;-). The problem is not > how in theory (patch the caller), but how in the LLVM code generation > process. There are three steps for that: > > 1) How to represent the stub in the IR? An intrinsic? An external field > with a ghost linkage? Probably an intrinsic. The trick is making it

BGB wrote: > > for x86: > I presume LLVM supports inline assembler, and also uses the traditional > frame pointer-based stack layout, but I don't know the details (people who > know LLVM could probably be more helpful here). > > ok, maybe here is an option: > after getting the value (in the created stub), execute a chunk of inline > assembler to modify the caller