<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi everyone,<div class=""><br class=""></div><div class="">In the current version of the stackmap format (v1), it is not possible to associate callsites with their respective functions. This seriously limits the usefulness of the stackmaps, since one cannot walk a stack (for the purposes of, say, GC) unless this is fixed. </div><div class=""><br class=""></div><div class="">I have put together a patch that remedies this problem, but this requires changing the format of stackmaps very slightly (one extra field per function entry emitted). </div><div class=""><br class=""></div><div class="">Our plan is to bump the stackmap version number supported in LLVM from 1 to 2 so that external tools do not have silent breakages. We will also be dropping support for parsing/emitting version 1 maps in LLVM once this patch is merged into trunk, since this is mostly a bugfix for v1-style maps. (see here for more details: <a href="https://reviews.llvm.org/D23487" class="">https://reviews.llvm.org/D23487</a> )</div><div class=""><br class=""></div><div class="">~kavon</div></body></html>