Summary: The Java frontend creates a single `tenv` file per `javac` invocation, but the code loading the `tenv` for a given Java procedure in the backend was not taking advantage of it. Also, with the lazy dynamic dispatch algorithm, the procedure name can be created on-demand and therefore defeat the approach to load the tenv by looking at the call graph to associate existing procedure names to the corresponding serialized tenv file. This diff should also fix this last point. Reviewed By: sblackshear Differential Revision: D4969254 fbshipit-source-id: 66ed318master
parent
78a7865f2a
commit
b790ac8c14
Loading…
Reference in new issue