Provide alignment guarantees for embedded binary data

[lorcanmooney]

dotnet/runtime#60948 requires that embedded data should be aligned to match the pimitive data type, but even in the absence of that feature, it would be good to provide some sort of alignment guarantees for raw byte data. This would allow us to overlay a ReadOnlySpan of custom structs on the embedded data.

I imagine 8-byte alignment would be the minimum, but I can imagine anything up to 64-bytes being useful.

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[Sergio0694]

This would be very useful for blitting GUIDs over static spans, which is eg. done extensively in TerraFX.Interop.Windows (cc. @tannergooding). This also came up in microsoft/CsWinRT#1058 (comment).

[jcouv]

We have a PR that's updating the compiler to make use of new CreateSpan(FieldHandle) API, which will allow optimizations on (ReadOnlySpan<TYPE>)new TYPE[] { ...constants... } to kick in for other types than byte.
As part of that PR, we're doing two things:
1. verifying the alignment of the blobs emitted (currently we always align to 8-bytes, but this could become more granular in the future, ie. compacting more while respecting the alignment required by a given type)
2. emitting .pack flags that capture the alignment requirement for each blob (this is used by IL rewriters)

I believe those two address your needs described above. Let me know if that's not the case.

[jcouv]

Retracted my comment above. Upon re-reading, I think you're asking about alignment guarantees outside of this scenario.
Could you provide a specific example to make sure we're on the same page?

[Sergio0694]

So, not sure about OP, but for my use case scenario, as well as TerraFX, consider this:

public static ref readonly Guid CLSID_D3D12Debug
{
    [MethodImpl(MethodImplOptions.AggressiveInlining)]
    get
    {
        ReadOnlySpan<byte> data = new byte[] {
            0xEB, 0x2A, 0x35, 0xF2,
            0x84, 0xDD,
            0xFE, 0x49,
            0xB9,
            0x7B,
            0xA9,
            0xDC,
            0xFD,
            0xCC,
            0x1B,
            0x4F
        };

        return ref Unsafe.As<byte, Guid>(ref MemoryMarshal.GetReference(data));
    }
}

This is used extensively in TerraFX (like, there's thousands of these), and it's a neat trick that can completely get rid of static constructors in cases like this, which greatly improves startup performance, and also reduces binary size. Now, this is technically undefined behavior given that a GUID should be aligned to 8 bytes boundaries. This can be worked around by generating the blittable sequence as a span of two long-s, as that'd then get the correct alignment for the RVA field (this idea was from @AaronRobinsonMSFT). This is kinda clunky thought, as you'd have to manually compute the right constants by combining groups of bytes into long-s, plus it wouldn't really be flexible (nor allow greater alignment if needed, say if someone wanted to build a complex lookup table to then load with SIMD instructions, where you might want alignment to 64, 128 or 256 bytes boundaries, or whatever).

As far as I understand, right now .NET 7/C# 11 will only provide alignment guarantees for the primitive used in the span, which means it's restricted to the supported primitive types, and it has the issue mentioned above in case you want a sequence of just bytes, but with an alignment greater than 1. It would be nice to be able to somehow just indicate the byte alignment for the generated .text field for a blitted span 🙂

cc. @tannergooding

[tannergooding]

An example would be, for example, declaring the below, but providing some way for it to have 16-byte alignment

static ReadOnlySpan<uint> Data => new uint[] { 0, 1, 2, 3 };

This would allow it to be used with Vector128<uint> and aligned loads. There are other cases like Int128, UInt128, and other user-defined structs where one might want a higher than default guarantee on alignment.

I don't think this is strictly crucial for .NET 7, particularly given it would be hard to describe such arbitrary alignment support in all the relevant places. But it may be a good future consideration.

[tannergooding]

Now, this is technically undefined behavior given that a GUID should be aligned to 8 bytes boundaries

Just noting @Sergio0694, Guid on Windows only needs/expects 4-byte alignment since it is a struct Guid { uint _x; ushort _y; ushort _z; fixed byte _w[8]; } effectively.

[Sergio0694]

Ah, well then we only need to use a ReadOnlySpan<int> and reinterpret that, though still clunky ahah 😄
It would really be nice to just be able to indicate arbitrary alignment in some way.

Completely spitballing here, but I can imagine just using an attribute, though there's the issue that C# currently doesn't support attributes on locals (even though AFAIK they're allowed in IL as per ECMA spec, right?). That is, something like this:

[Align(16)]
static ReadOnlySpan<uint> Data => new uint[] { 0, 1, 2, 3 };

// And for locals
public static ref readonly Guid CLSID_D3D12Debug
{
    get
    {
        [Align(4)]
        ReadOnlySpan<byte> data = new byte[] {
            0xEB, 0x2A, 0x35, 0xF2,
            0x84, 0xDD,
            0xFE, 0x49,
            0xB9,
            0x7B,
            0xA9,
            0xDC,
            0xFD,
            0xCC,
            0x1B,
            0x4F
        };

        return ref Unsafe.As<byte, Guid>(ref MemoryMarshal.GetReference(data));
    }
}

Just saying, it'd be neat if something like this was looked at in the future 😄

This would be kinda similar to how you can __declspec(align(N)) in C++ etc.

[jkotas]

Ah, well then we only need to use a ReadOnlySpan and reinterpret that, though still clunky ahah

That still does not fully address the problem since the Guids created this way are non-portable. They won't work on big-endian machines.

dotnet/designs#46 proposal tried to fully address the problem. If we want to do something here, it should be something along these lines.

[Sergio0694]

"That still does not fully address the problem since the Guids created this way are non-portable. They won't work on big-endian machines."

Oh, yeah no, of course. To clarify, that specific comment was just meant to apply in the context of TerraFX.Interop.Windows, where big-endian is not an issue anyway as it's not one of the supported platforms. That would not be a general solution, absolutely 👍