Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- %S - too many type arguments (%d) - giving up compiling to MDIL
- Too many basic blocks in the inlinee.
- Error compiling inlinee
- Inlining requires new LclVars and we already have too many locals.
- Instruction size underestimated - estimate was %d, actual is %d
- Windows Phone OS 7 compatibility - Inlinee contains control flow.
- Inlinee contains SWITCH instruction.
- Windows Phone OS 7 compatibility - Inlinee contains prefix.
- Windows Phone OS 7 compatibility - Inlinee contains throw.
- Unsupported opcode for inlining.
- Windows Phone OS 7 compatibility - out of order ldarg.
- Windows Phone OS 7 compatibility - address taken.
- Inlinee writes to an argument.
- Too many local variables in the inliner
- Virtual call
- Tail call
- Caller needs security check.
- Not an inline candidate.
- Might turn into an intrinsic
- Needs security check
- Localloc used
- checked class constructor call
- Need to copy return buffer
- Constraint call in generic codeWill not expand this INLINECANDIDATE
- Recursive or deep inline recursion detected. Will not expand this INLINECANDIDATE
- Inlining failed due to an error during invoking the compiler for the inlinee
- Inlining failed due to an exception during invoking the compiler for the inlinee
- Inlining failed because inlinee did not contain a return expression.
- Cannot inline generic dictionary lookup
- Failed to init class
- Caller is synchronized
- Caller requires a security check.
- Inline failed due to cross security boundary call.
- Inlinee needs own frame for security object
- Inlinee calls a method that uses StackCrawlMark
- Inlinee uses delegate invoke
- Native VarArgs not supported in inlinee
- VarArgs not supported in inlinee
- inlining virtual calls on generic functions not supported.
- Cannot inline complicated handle access
- Calling through LDVIRTFTN
- Inlinee calls through code pointer
- Callee is native
- Cannot embed PInvoke cookie across modules
- PInvoke calli
- Cannot embed Var Args handle across modules
- Array method.
- Return types don't match
- Cross assembly inline failed due to NoStringInterning
- Inline failed due to LDARGA on something other than a variable.
- Inlinee contains NULL pointer for LDELEM
- Inlinee contains LEAVE instruction
- Inline failed due to ldvirtftn on non-virtual function.
- return type is composite
- Inline failed due to cross assembly call to a boundary method.
- Inlinee requires field access helper.
- ldsfld of valueclass
- Reaching CEE_THROW with too many things on the stack.
- No inlining for THROW within a non-void conditional
- CLR: Invalid x86 breakpoint in IL stream
- bad arg num
- bad loc num
- Return types are not matching.
- Native estimate for function size exceeds threshold.
- Inlinee contains EH.
- Inlinee has no body.
- Inlinee is vararg.
- Inlinee has too many locals.
- Inlinee has too many arguments
- Method is too big.
- Method's MaxStack is too big.
- Windows Phone OS 7 compatibility - Method is too big.
- Windows Phone OS 7 compatibility - Inlinee has locals.
- Windows Phone OS 7 compatibility - float return.
- Windows Phone OS 7 compatibility - float argument.
- Could not get method info.
- Inlinee's class could not be initialized.
- VM rejected inline
- Cannot inline MDIL cross-module.
- Cannot inline across MarshalByRef objects.
- Exception while inspecting inlining candidate.
- Argument contains mkrefany
- Argument has side effect.
- Method is called with null this pointer.
- Arguments 'int <- byref.
- Method has pinned locals.
- Compiling debug code.
- Call site marked as tailcall.
- Not a direct call.
- Inlinee is a helper call.
- Not a direct managed call.
- Will not inline blocks that are in the catch handler region.
- Will not inline blocks that are in the filter region.
- Method is marked as no inline or has a cached result.
- Inlinee is native or synchronized.
- Inliner requires a security check.
- Inlinee is NoMetadata
- Inlinee is debuggable
- Profiler disabled inlining globally
- Inlinee is not verifiable
- Inlinee is marked as no inline
- Inlinee requires a security object (calls Demand/Assert/Deny)
- Inlinee is MethodImpl'd by another method within the same type
- Inlinee has restrictions the JIT doesn't want
- Windows Phone OS 7 compatibility
- Caller is ComImport .cctor
- Caller has declarative security
- Different security
- Caller is the entry point
- Caller is marked as no inline
- Callee might have a StackCrawlMark.LookForMyCaller
- Caller is a CER root
- Jit reported error 0x%x while compiling 0x%p
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement