One more: Method invalidation for strange example code

[Andreas Woess]

No uncommon trap? Interesting... I will look into it. What should I run?
Richards? Small tests to reproduce are always good.

- andreas

On 23.01.2014 10:44, Stefan Marr wrote:
> Hi:
>
> On 22 Jan 2014, at 14:11, Stefan Marr <java at stefan-marr.de> wrote:
>
>> Any hints how I could track what causes the invalidation? All invalidations done in TruffleSOM directly are tracked, in my version locally, I think.
> Just to give an idea what I mean with that: https://gist.github.com/smarr/8575659
> This sprinkles printlns into all the relevant places I could identify.
> And with that, I am kind of sure that nothing directly from the Truffle level is causing the invalidations.
>
> So, is there any way to attach more information to an InvalidInstalledCodeException?
> The invalidation reason is not showing up in the hotspot log, and it’s not an uncommon trap either.
>
> Beside guessing and applying random changes, I am really a little helpless here.
> Perhaps, there is a way to add more debugging information into the generated native code?
> Could someone point me perhaps in the main direction for what I could be looking in the Graal code base?
>
> Thanks
> Stefan
>
> PS: and there is another issue with non-local returns I think. But I wasn’t able yet to produce a condensed test case.
>
>


---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com