Andy Ayers

>> @danmoseley is a 63line method a candidate for inlining? > There are various rules and heuristics, and it may depend on the caller. Cc @AndyAyersMS for thoughts Probably not,...

FYI, @echesakovMSFT did some work on this a while back; figured I'd link up the parts here. dotnet/coreclr#6653 refactored the jit to create a framework where one can plug in...

There are various tradeoffs involved in determining where and how one might do escape analysis. The compiler (and here I presume by *compiler* you mean CSC) has limited visibility into...

I don't believe it does escape analysis. @davidwrighton might know more though.

Hmm, Egor's fork seems to be dead. Trying to see where the code went. @echesakov ?

Thanks!

Egor restored the branch and I updated it to build versus master here: [master...AndyAyersMS:StackAllocation](https://github.com/dotnet/coreclr/compare/master...AndyAyersMS:StackAllocation). Also started looking into what it would take to stack allocate a simple delegate that is...

I suppose so, though it is a funny kind of advantage. There is a natural tension in places between doing optimizations very early, when generating IL, or waiting until later...

Brief update: * importer doesn't know that some temps are inherently non-null, so can't fold away the null this in delegate check. This fact eventually surfaces during optimizations but this...

Did some prototyping on top of the changes above to get the delegate to be promotable. Lots of things to sort through on the way: * Updated the object allocation...