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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment