#code stripping for burst compiled code in IL2CPP
1 messages · Page 1 of 1 (latest)
It comes up periodically but hasn't been specifically scheduled to happen to my knowledge; I imagine it'll happen eventually though. Possibly as burst continues to grow in usage it'll get higher priority
Currently the fact that we don't strip those methods means that you can turn off burst after the fact by removing lib_burst_generated.dll on some platforms, which can be occasionally useful
It actually saved us on launch
Fixed an issue when targeting multiple cpu architectures (e.g. SSE2 & AVX2) that under some circumstances would lead to code attempting to execute paths not designed for that cpu.
When we launched we had this issue and quite a few of our users would just crash at a certain point and we were able to provide them instant support by getting them to delete the burst dll until it was fixed. That was a happy find to know the app still worked without it.