MethodImplOptions.AggressiveInlining vs TargetedPatchingOptOut
11,120
I was waiting to see if someone else could have a better answer but it seems no.
After I read dtb comment I did a little bit more research and found this http://blogs.microsoft.co.il/blogs/sasha/archive/2012/01/20/aggressive-inlining-in-the-clr-4-5-jit.aspx.
My understanding of this post is that you can apply both attribute AggressiveInlining will remove the in-lining size limit of the method while like dtb said the TargetedPatchingOptOut will allow inlining accross assembly boundaries.
Related videos on Youtube
31 : 00
Demo: Using PyOptSparse, primarily with IPOPT, for Nonlinear Optimization in Python
05 : 27
What is the Critical Path Method (CPM)? PM in Under 5 minutes
21 : 18
Boosting Machine Learning Tutorial | Adaptive Boosting, Gradient Boosting, XGBoost | Edureka
06 : 42
Targeted Individual Tips For Targeted Individuals Dealing with DEW or Mind Control Weapons
12 : 53
Text Classification 3: Passive Aggressive Algorithm
05 : 47
34- Pandas DataFrames: Aggregation
42 : 54
Writing Allocation Free Code in C#
06 : 37
Locking on this vs. MethodImplOptions.Synchronized
11 : 40
CE64-08 Antimicrobial Recommendation in Pets Using ML and Imbalanced Dataset Problem Solving
32 : 59
Vetting data processors: Most common flaws and issues
02 : 04
Why do stdstring operations perform poorly - PYTHON
09 : 33
4 Oversampling and Undersampling Methods for Imbalanced Classification Using Python
03 : 44
#Programming - Aggressive vs Defensive Code
01 : 36
ModelAdmin thread-safety/caching issues - Django
02 : 00
Django, Python 3 & Postgres - mod_wsgi issue - Django
01 : 56
Why are arbitrary target expressions allowed in for-loops - PYTHON
Author by
Yann Lebel
Updated on June 04, 2022Comments
-
Yann Lebel about 2 years
What is the difference between the MethodImplAttribute with the option
MethodImplOptions.AggressiveInliningand theTargetedPatchingOptOut?When I searched on Google everybody seems to says that both (might) inline the method but without giving the difference.
-
Feidex over 11 yearsTargetedPatchingOptOut is quite well explained here: stackoverflow.com/questions/6109745 The crucial part seems to be that the inlining is performed across assembly boundaries, which is not done by default. I would expect that AggressiveInlining is a hint to inline the method, but unlike TargetedPatchingOptOut does not allow inlining across assembly boundaries.
-
BlueRaja - Danny Pflughoeft about 11 years@dtb and Yann: See here. tl;dr: inlining across assembly bounds is already done by the JIT for everything but the .Net core library, whereTargetedPatchingOptOutis useful. For everyone else (all of us),TargetedPatchingOptOutis completely useless.
-
-
eug over 10 yearsAs mentioned above, don't apply TargetedPatchingOptOut in your own code - see stackoverflow.com/a/14982340/94078
