re: JIT ETW Inlining Event Fail Reasons

Surupa Biswas — Mon, 09 Nov 2009 07:38:44 GMT

Tanveer,

Yes, indeed - there are a whole bunch of messages in the NGen output related to missing dependencies, profile data et al when installing various managed applications and frameworks. In general, as long as the compilation of an assembly doesn't fail (no "error compiling") it means a native image was successfully generated in spite of these issues (we end up with "partial native images" that fall back to JIT compilation for the "missing pieces" - assuming they're available at runtime i.e.). We still do try to look through the warnings and clean them up when possible, but they're not really what we treat as functional/correctness issues. Errors during compilation (where NGen returns -1) are definitely bugs, however.

Hope that helps.

Surupa Biswas

CLR Codegen Team

re: JIT ETW Inlining Event Fail Reasons

Tanveer Badar — Sat, 07 Nov 2009 10:10:41 GMT

I was wondering if anyone could elaborate something for me. When running ngen.exe binding failures, ref-def mismatches, dependencies not getting resolved and a whole host of other errors are often observed. These errors happen for assemblies owned by teams inside microsoft too, like VS, Office, SQL server etc. Do these failures to generate native images classify as bugs, as in, someone somewhere forgot something or not?