Additional parameters execute method

[Renze Torensma]

Hi Chris,

Thanks for your aswer! At first I thought the execute method was something special the compiler knew how to optimize it, but that’s not the case I understand?
And if I understand correctly the execute(VirtualFrame) is called by the CallTarget.call method (line 382 in com.oracle.graal.truffle.OptimizedCallTarget), so I would have to call my execute(VirtualFrame, Context) from the execute(VirtualFrame) for it to be used when a calltarget is called?

Renze

> On 11 mei 2015, at 01:27, Chris Seaton <chris.seaton at oracle.com> wrote:
> 
> Hi Renze,
> 
> The only execute method which is mandated is the abstract one in RootNode. That is execute(VirtualFrame). In your own nodes you can have whatever signature you want. There isn’t anything special about execute(VirtualFrame) in that case, so you can certainly have execute(VirtualFrame, Context), or any other signature.
> 
> Chris
> 
>> On 11 May 2015, at 00:24, Renze Torensma <renzetorensma at gmail.com> wrote:
>> 
>> Nobody knows? :(
>> 
>>> On 5 mei 2015, at 01:24, Renze Torensma <renzetorensma at gmail.com> wrote:
>>> 
>>> Hi,
>>> 
>>> I was wondering whether it would be possible to add parameters to the execute method, for example a custom context aside from the VirtualFrame. So for example the execute method would be execute(VirtualFrame frame, Context context) instead of execute(VirtualFrame) like it is in SL and JRuby.
>>> 
>>> Best regards,
>>> Renze
>> 
>