Search Issue Tracker
Fixed
Fixed in 1.8.28
Votes
0
Found in [Package]
1.8.27
Issue ID
BUR-2932
Regression
No
Mathematics hash function returns different results when compiled with Burst and Mono
How to reproduce:
1. Open attached project "IN-124637"
2. In the menu bar click on "Test/Burst Compiled"
3. In the menu bar click on "Test/No Burst Compiled"
4. Observe Console
Expected result: Result is the same across both methods
Actual result: Results are different
Reproducible with: 1.2.6 (2023.1.0a3), 1.3.3 (6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a1)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- passing more than one parameter into "f()" results in expected behavior
- issue reproduces with hash(uint3), hash(int3), hash(float3)
- issue does not reproduce with hash(uint2), hash(uint4), hash(int2) hash(int4), hash(float2), hash(float4), hash(bool3), no other methods 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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Fixed that Burst would miscompile arithmetic under very specific circumstances
Resolution Note (fix version 1.8.28):
Fixed that Burst would miscompile arithmetic under very specific circumstances
Resolution Note (fix version 1.8.28):
Fixed that Burst would miscompile arithmetic under very specific circumstances