Incorrect unsigned integer (uint) value comparisons are made when min() & max() functions are used with [BurstCompile(FloatPrecision.Low, FloatMode.Fast)]

Package: Burst

Fixed

1.8.X

1.8.25

How to reproduce:
1. Open the attached project “IN-108878“
2. Open the window "Test Runner"
3. Find BuildBvhTest(20)
4. Right Click on BuildBvhTest(20)
5. Select “Run“
6. Open the window “Console“
7. Observe the Console

Expected result: A message is outputted in the Console “uint4(2393899008, 2393899008, 2393899008, 2393899008)“
Actual result: A message is outputted in the Console “uint4(1930428160, 2393899008, 2037382914, 2393899008)“

Reproducible with: 1.8.21(6000.0.54f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a2)
Could not test with: 1.8.20(6000.2.0a1) (Package error)

Reproducible on: Windows 11 Enterprise
Not reproducible on: No other environments tested

Workaround: Use [BurstCompile] with default settings

Incorrect unsigned integer (uint) value comparisons are made when min() & max() functions are used with [BurstCompile(FloatPrecision.Low, FloatMode.Fast)]

Package: Burst

Fixed

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Incorrect unsigned integer (uint) value comparisons are made when min() & max() functions are used with [BurstCompile(FloatPrecision.Low, FloatMode.Fast)]

Package: Burst

Statuses

Fixed

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?