Long Vector Execution Tests: Add test cases using min precision values

[alsepkow]

We should add test cases for min16float, min16int, and min16uint where applicable.

These types do not make use of the -enable-16-bit-types flag.
They are allowed to be computed at a minimum of 16-bits, but do not guarantee 16-bit truncation/wrapping/overflow behavior. Nor do they support any FP specials, like INF/NaN/denorm.

[alsepkow]

Implementation Plan for Min Precision Type Tests

Copilot created a detailed plan for adding test cases for min16float, min16int, and min16uint to LongVectors.cpp.

Summary

• Goal: Add comprehensive test coverage for min precision types that don't require -enable-16-bit-types flag
• Approach: Follow patterns from equivalent base types (min16int→int16_t, min16uint→uint16_t, min16float→HLSLHalf_t)
• Test Class: Add to existing DxilConf_SM69_Vectorized_Core test class
• Test Data: Reuse existing input datasets - no new datasets needed

Key Findings

Test Data Infrastructure:

• Min16int/uint can reuse int16_t/uint16_t input datasets directly
• Min16float can use HLSLHalf_t datasets (FloatSpecial input set exists but isn't currently used, so lack of FP special support won't be an issue)

Implementation Steps

1. Define min precision data types

   • Add DATA_TYPE macro definitions for min16float, min16int, and min16uint
   • Set appropriate HLSL type strings and size information

2. Add min16int test cases

   • TernaryMath: Mad
   • BinaryMath: Add, Subtract, Multiply, Divide, Modulus, Min, Max
   • Bitwise: And, Or, Xor, LeftShift, RightShift, ReverseBits, CountBits, FirstBitHigh, FirstBitLow
   • Unary: Initialize, ArrayOperator (Static/Dynamic)
   • Casts and WaveOps where applicable

3. Add min16uint test cases

   • Same operation categories as min16int following uint16_t pattern

4. Add min16float test cases

   • TernaryMath: Mad
   • BinaryMath: Add, Subtract, Multiply, Divide, Modulus, Min, Max, Ldexp
   • Bitwise: Saturate
   • Unary: Initialize, ArrayOperator (Static/Dynamic)
   • Casts and WaveOps where applicable

5. Build and verify tests

   • Build the test suite
   • Run newly added min precision type tests
   • Verify compilation and execution

Dependencies

Steps 2-4 depend on step 1 completing. Step 5 depends on steps 2-4 completing.