{"action":"opened","issue":{"url":"https://api.github.com/repos/dotnet/coreclr/issues/1957","labels_url":"https://api.github.com/repos/dotnet/coreclr/issues/1957/labels{/name}","comments_url":"https://api.github.com/repos/dotnet/coreclr/issues/1957/comments","events_url":"https://api.github.com/repos/dotnet/coreclr/issues/1957/events","html_url":"https://github.com/dotnet/coreclr/issues/1957","id":115132167,"number":1957,"title":"Need some way for the jit to reliably identify methods across runs","user":{"login":"AndyAyersMS","id":10121823,"avatar_url":"https://avatars.githubusercontent.com/u/10121823?v=3","gravatar_id":"","url":"https://api.github.com/users/AndyAyersMS","html_url":"https://github.com/AndyAyersMS","followers_url":"https://api.github.com/users/AndyAyersMS/followers","following_url":"https://api.github.com/users/AndyAyersMS/following{/other_user}","gists_url":"https://api.github.com/users/AndyAyersMS/gists{/gist_id}","starred_url":"https://api.github.com/users/AndyAyersMS/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AndyAyersMS/subscriptions","organizations_url":"https://api.github.com/users/AndyAyersMS/orgs","repos_url":"https://api.github.com/users/AndyAyersMS/repos","events_url":"https://api.github.com/users/AndyAyersMS/events{/privacy}","received_events_url":"https://api.github.com/users/AndyAyersMS/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-04T19:45:50Z","updated_at":"2015-11-04T19:45:50Z","closed_at":null,"body":"The `methodHash` provided to the jit via the jit interface is supposed to provide this, but it's not unique. Neither are names or tokens.\r\n\r\nIdeally this method ID would be independent of jit behavior (eg LLILC and RyuJit would see the same IDs even if they make different demands via the jit interface). \r\n\r\nI'd be willing to settle for something that works only in crossgen to start with.\r\n\r\nWithout something like this it's going to be challenging to correlate inlining data across runs and implement things like log replay."}}