Search Issue Tracker
Fixed
Fixed in 1.8.4
Votes
0
Found in [Package]
1.8.4
Issue ID
BUR-2382
Regression
No
Choosing ARMV9A in burst inspector on M1 Mac formats assembly wrong
I'm on a M1 Mac. I'm using Unity 2021.3.24f
To recreate:
Add the follow test to BurstInspectorGUITests.cs in the Unity.Burst.Tester project (it is already part of it, but in case it'd be missing this will show the error):
{code:java}
[BurstCompile]
private struct MyJob : IJob
{
[ReadOnly]
public NativeArray<float> Inpút;
[WriteOnly]
public NativeArray<float> Output;
public void Execute()
{
float result = 0.0f;
for (int i = 0; i < Inpút.Length; i++)
{
result += Inpút[i];
}
Output[0] = result;
}
}
{code}
Afterwards open the burst inspector and the "MyJob" in Assembly.
Choose "ARMV9A" in the processor options.
Note how all the text is incorrectly formated + loop lines are not appearing.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment