Segmentation fault/ICE when attempting a particular (invalid) code pattern

Description

AFAICT, there is no way to perform interlocked instructions on data viewed via templated loads or stores with ByteAddressBuffers. However, attempting to do so ICEs the compiler.

Steps to Reproduce

Here's a simple snippet to demonstrate the issue:

struct T
{
    uint value;
};
RWByteAddressBuffer b = ResourceDescriptorHeap[0];
int original;
InterlockedMax(b.Load<T>(0).value, 1, original);

Obviously, the code above doesn't make any sense, but since the compiler ICEd instead of reporting a diagnostic, I decided to file this as an issue.

As an aside, is there a way to express the intent above with valid HLSL today? (I don't believe it's possible, but it would be nice if it was).

Environment

• DXC version trunk and 1.7
• Host Operating System Windows

Start by reproducing the ICE with the provided HLSL snippet using DXC trunk and version 1.7 on Windows. Trace the compiler path handling the templated ByteAddressBuffer load used as an interlocked-operation operand, and consider the diagnostic for this invalid pattern as done.