com.unity.burst 1.8.0
Notes: processedReleased September 23, 2022
Unity Compatibility
Minimum Unity: 2020.3
Package Dependencies
✨ Features
- Added experimental atomic and/or operations to Burst.
📈 Improvements
- `math.fmod` in combination with a Burst job compiled with `FloatPrecision.Low` will now generate a more optimized low-precision version of the function.
- Burst now respects the checkbox "Enable Armv9 Security Features for Arm64" in the Player settings, making Android builds generate PAC/BTI instructions if enabled.
- In Burst AOT Settings, only the relevant CPU Architectures dropdowns for the current build target and architecture are now displayed
- The callstack of the invalid external call is now included when reporting BC1091
- Changed so code is focused when branch arrows are present.
- Changed so Burst reported errors are not collapsible.
⚡ API Changes
🔧 Bug Fixes
- An Internal Compiler Error that could occur if a function that requires a struct ret (due to ABI) has been discarded by other logic.
- Fixed a bug with locally declared array variables in functions where storing `null` into them could cause invalid codegen.
- Fixed a bug in Burst player builds where sufficiently complicated Bursted code could cause a deadlock deep within LLVM.
- Fixed that UWP builds wouldn't respect the specified "Target SDK Version" and "Visual Studio Version" settings
- Fixed Burst inspector sometimes freezing when selecting between blocks.
- Fixed the Burst Inspector sometimes becoming unresponsive when selecting text.
- Fixed a race condition with the Burst log timings such that previously reported results could be included in subsequently reported timings.
- Fixed the managed fallbacks for `bzhi` and `bextr` to match what the native hardware instructions do.
- Fixed a bug in the static readonly constant expression evaluation (what we call the IL interpreter) whereby it would not truncate unsigned integers correctly.
- Fixed incorrect code-gen when a function is both used normally and as a function-pointer
⚠️ Known Issues
- The PDB path associated with the Windows Player dll is incorrect, resulting in broken symbols.
