Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.8.0-pre.1
Issue ID
BUR-1708
Regression
No
The second parameter type in "X86.Sse4_2.crc32_u64" is "long" while it should be "ulong"
Reproduction steps:
1. Observe the crc32_u64 method second parameter type in Unity Burst Intrinsics
2. Observe the crc32_u64 method second parameter type in Microsoft docs
3. Observe the crc32_u64 method second parameter type in Intel Intrinsics
Expected result: The parameter type in Unity Burst Intrinsics does not differ
Actual result: The parameter type in Unity Burst Intrinsics is "long" while in Microsoft docs and Intel Intrinsics the parameter type is "ulong"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- A black bar appears on the Game View toolbar when the Game View is resized vertically
- Double separation lines are present in Override Controls in a DefaultVolumeProfile Asset
- Silent crash when multiple child GameObject Colliders are triggered while attached to a Parent GameObject with Transform Scale set as (0; 0; 0)
- Numbers of output expressions does not match number of output error is thrown when converting node to property Output
- GameObjects with higher Render Queue values are being reflected on GameObjects with lower Render Queue values
Add comment