On 14 March 2017 at 20:48, Vladimir Ivanov <[email protected]> wrote: > Just in case it will cause problems for you, there's a workaround: you can > prune @HotSpotIntrinsicCandidate during instrumentation.
Wouldn't that just cause the 2nd warning to disappear, but the first one would remain? /Michael
