Search Issue Tracker
Fixed
Fixed in 1.8.17, 2.0.0-pre.18
Votes
0
Found in [Package]
1.8.14
Issue ID
BUR-2661
Regression
No
255 is returned when setting an enum variable to 1 and casting it to a negative integer
How to reproduce:
1. Open the attached “BurstBug.zip“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter Play Mode
Expected result: “Result 1: -1; Result 2: -1; Result 3: -1“ is logged twice
Actual result: “Result 1: 255; Result 2: 255; Result 3: -1“ and “Result 1: -1; Result 2: -1; Result 3: -1“ is logged
Reproducible with: 1.4.0, 1.5.1 (2021.3.35f1), 2.4.0-pre.2 (2022.3.20f1, 2023.2.12f1, 2023.3.0b9)
Reproducible on: macOS 14.2.1 Sonoma (Intel)
Not reproducible on: No other environment tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Resolution Note (fix version 2.0.0-pre.18):
Negation of enum values now correctly promotes from the underlying type.
Resolution Note (fix version 1.8.17):
Enums where not correctly promoted before a negate instruction, burst now correctly promotes a byte (and other types) enum to int as per spec.