[Truffle] Eliminating Calls to Side-Effect Free Methods?

Stefan Marr java at stefan-marr.de
Wed Mar 12 15:18:50 UTC 2014


Hi Chris:

On 12 Mar 2014, at 16:12, Chris Seaton <chris at chrisseaton.com> wrote:

> This is how Ruby does it, and it does go to nothing.

I should have mentioned: I tried that in the morning ;)

Well, I did not introduce any executeVoid, because generally everything is an expression with a return value.
But I tried to rewrite the SequenceNode based on what I saw in your Ruby implementation. Also, because my pervious not so good experience with @ExplodeLoop. But, the effect was zero.
Normally, the PE should see that `last` is never read but at the end.

Is the executeVoid an essential thing? Did you notice any difference with having it/not having it?

Thanks
Stefan

-- 
Stefan Marr
INRIA Lille - Nord Europe
http://stefan-marr.de/research/





More information about the graal-dev mailing list