The profile fixup introduced in JDK-8166750 would produce invalid results with -XX:TypeProfileWidth=1.

On Oct 26, 2017, at 9:48 AM, Tom Rodriguez <tom.rodriguez@oracle.com> wrote:

Sorry I'm late to this, but I don't think the HotSpotMethodData changes are correct. If you run with -XX:TypeProfileWidth=1 you'll get incorrect profiles for non-statically bindable call sites. Shouldn't it be entries == 1 && methods[0].canBeStaticallyBound()? I think the ciMethod workaround for this problem has the same issue. Also I think it would make sense to null out the entry so it looks the same as a properly profiled vfinal call site.