Inliner refactoring: consolidate logging, reporting and dumping
authorAndy Ayers <andya@microsoft.com>
Thu, 4 Feb 2016 07:01:42 +0000 (23:01 -0800)
committerAndy Ayers <andya@microsoft.com>
Fri, 5 Feb 2016 23:12:25 +0000 (15:12 -0800)
commit82ec59e3c8eb287cd9c1c2f1efb806518ee9a14e
tree419bf76cec8311a1c01ef82015a0be7164d1d154
parent6b039c47b9c7ab96c07d83dd3b1cc83ca5cc01db
Inliner refactoring: consolidate logging, reporting and dumping

With this change the responsibility for dumping, logging, and reporting
inline decisions is moved into the JitInlineResult class instead of being
distributed throughout the code base. This insures all the relevant inline
information is handled in a consistent manner.

The JitInlineResult is updated to hold a compiler instance and now
requires a context string describing the what the jit is doing as it evaluates
an inline candidate. There are 4 distinct contexts in use currently.
src/jit/compiler.cpp
src/jit/compiler.h
src/jit/flowgraph.cpp
src/jit/importer.cpp
src/jit/morph.cpp