You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three examples. In all three its happeing on array flattened values.
96x error: Internal declaration 'bTile.scalarized.1dim' is unused.
64x error: Internal declaration 'aTile.1dim' is unused.
32x error: Internal declaration 'aTile.scalarized.1dim' is unused.
Its curious that there was anything to flatten in these cases since we flatten after optimizations. I suspect these two types were used in a function that was cleaned up by Finalize Linkage but the global lived on.
However maybe this code should live at the start of our lowering pipeline. I think it makes the most sense to do something like this in DXILFinalizeLinkage. Alternatively we could wait for: llvm/wg-hlsl#272
The text was updated successfully, but these errors were encountered:
Three examples. In all three its happeing on array flattened values.
Its curious that there was anything to flatten in these cases since we flatten after optimizations. I suspect these two types were used in a function that was cleaned up by Finalize Linkage but the global lived on.
looking at:
I see these two and they are defined but not used. We should probably delete them if this is the case.
@aTile.1dim = local_unnamed_addr addrspace(3) global [64 x i32] zeroinitializer, align 4
@bTile.scalarized.1dim = local_unnamed_addr addrspace(3) global [512 x i32] zeroinitializer, align 4
We could add a check for uses to both DXILDataScalarization.cpp and DXILFlattenArrays.cpp. If there are no uses then we just delete and don't do transformations.
this is fixed by:
However maybe this code should live at the start of our lowering pipeline. I think it makes the most sense to do something like this in
DXILFinalizeLinkage
. Alternatively we could wait for: llvm/wg-hlsl#272The text was updated successfully, but these errors were encountered: