Using [BurstCompile] On Methods

Adding the attribute to a static method makes it show up in the Burst Inspector. Do these compiled methods actually get called from managed nonjob code? e.g. calling SomeClass.Method() from a Monobehavior.Update().

Code (CSharp):

1. [BurstCompile]
2. public unsafe class SomeClass
3. {
4.     [BurstCompile]
5.     public static void Method()
6.     {
7.         // do stuff
8.     }
9. }

 

It discussed on this forum more than once. Use search instead of duplicating threads.
One of latest:
https://forum.unity.com/threads/can...rmal-static-class-method.695398/#post-4650307

 

Thanks, point taken; next time ill bump the most relevant thread i can find. What i found however doesn't answer my question.

They've said they plan to support pre-compiled methods in the future: https://forum.unity.com/threads/bur...atic-functions-in-builds.683797/#post-4595557

The methods are compiled and show up in the inspector, but my question is specifically if they're being executed. Are the methods being patched on build/play in the editor to point to the compiled method?

Im asking because from my tests the performance appears to be the same speed regardless of what kind of work is being done; which would seem to indicate that although they appear to be working, the burst compiled version is being completely ignored during build and play.

 

Pretty sure they are not being executed. Lots of people are waiting for burst support on non-job code.

 

Best solution so far is to put in ijob and .run - I think this was mentioned somewhere before