Search Issue Tracker
Fixed in 0.4.2-38
Votes
0
Found in [Package]
0.2.4-27
Issue ID
1101466
Regression
No
Unity burst compiler produces incorrect result when converting constant uint to ulong
To reproduce:
1) Open attached project and sample scene
2) Play it
In the center, a value for "ulong value = uint.MaxValue;" is shown
Expected (Burst Jobs disabled): 4294967295
Actual (Enabled): 18446744073709551615
-
nobare
May 11, 2019 06:59
Unity burst are going to compile the all details to produce the incorrect result it was when converting constant unit was ulong on this. You have to know how this was possible just read article on https://telstraeduaustralia.com/ozessay-com-au-review it has the all information that was available on this site having the all access on this.
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
- Character spacing value is not applied when using a specific font asset
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
Resolution Note (fix version 0.4.2-38):
Fixed in Burst 0.4.2-38