Short Answer: Your asd array is declared as this: int *asd=new int[16]; Therefore, use int as the return type rather than bool. Alternatively, change the array type to bool. In any case, make the return type of the test function match the type of the array. Skip to bottom for more details. Long Answer: In … Read more
You could use MethodImplAttribute and specify MethodImplOptions.NoInlining. [MethodImpl(MethodImplOptions.NoInlining)] void YourMethod() { // do something } Note that this still doesn’t guarantee that you can get at the actual calling method as seen in the source code. Your method won’t be inlined, but your method’s caller could be inlined into its own caller, etc etc.
A couple of the other answers have suggested that only final methods can be inlined – this is not true, as HotSpot is smart enough to be able to inline non-final methods so long as they haven’t been overridden yet. When a class is loaded which overrides the method, it can undo its optimisation. Obviously … Read more
It is a jitter implementation detail, the x86 and x64 jitters have subtly different rules. This is casually documented in blog posts of team members that worked on the jitter but the teams certainly reserve the right to alter the rules. Looks like you already found them. Inlining methods from other assemblies is most certainly … Read more
When executing a given piece of code, whenever you call a standard function the execution time is slightly higher than dumping there the code contained into that function. Dumping every time the whole code contained in a function is on the other end unmainteinable because it obviously leads to a whole mess of duplication of … Read more
The C++ and C standards leaves a bunch of freedom to compilers. Compilers are free to count to 1 billion between every instruction, or only do so if an integer has a prime value in it. Decent “real” compilers don’t do this. This is a quality of implementation issue. Inlining function objects into something like … Read more