Skip to content

Introduce generated COM graphics, DXC and DirectML foundation - #3

Closed
atcarter714 wants to merge 6 commits into
migration/net10-build-baselinefrom
migration/generated-com-foundation
Closed

atcarter714 wants to merge 6 commits into
migration/net10-build-baselinefrom
migration/generated-com-foundation

Conversation

@atcarter714

@atcarter714 atcarter714 commented Nov 5, 2026 •

Copy link
Copy Markdown
Owner

Adds a modern SDK path beside the proof-of-concept API: source-generated COM behind sealed C# owners, explicit graphics commands, DXC compilation and a separate DirectML component. The new samples depend only on this path. Stacked on #2; base: migration/net10-build-baseline.

  • Ownership and graphics: unique generated projections, deterministic release, scoped borrows, device-identity checks and native dependencies retained through GPU fence completion. Pending submissions root queues independently of application references. Includes local Agility factories, adapter/WARP selection, queues/lists/allocators, buffers/RTVs, root signatures/PSOs and flip HWND presentation.
  • DXC and DirectML: UTF-8 compilation, arguments, generated include/blob callbacks, copied outputs and separate diagnostics/status. DirectML supplies validated dense Float32 shapes, compiled equal-shape Add, initialization, temporary/persistent storage, descriptors, binding and synchronous execution.
  • Distribution and diagnostics: exact native SDK dependencies with transitive architecture-specific deployment; isolated package build/single-file publish and native hash checks; bounded triangle/GC-stress and numerical samples; process-scoped ProcDump launcher.

Validation: all four jobs passed for implementation commit 222112ad1f968dbad12693f6a7e1a1972bcd1ca5.

Gate Result
Windows Debug and Release Full solution build; three baseline tests; native fixture; packing; isolated consumer build/publish; native hashes and published debug-layer exclusion passed
Windows and Linux native fixture JIT and NativeAOT each passed 2,288 checks, with 2,004 native fixture objects destroyed and none left alive per run
Windows WARP, JIT with validation DXC compute/readback = 1234; DirectML Add = [11, 22, 33, 44]
Windows published NativeAOT console Repeated both numerical workloads successfully

The fixture exercises real C++ vtables, inherited slots and structure returns; QI/projection failures and cleanup; clones, borrows, disposal/finalization and GC; native-held callbacks; the generated DXC include/blob callbacks and HRESULT failure path; and DirectML descriptor layouts. The Windows gates caught and fixed a platform-dependent output-path assumption and stale thread-local COM error information from Marshal.GetHRForException.

Local Linux Debug/Release builds, packing, isolated consumer build/publish and JIT/AOT checks also passed. Local AOT required an external ILLink task-host workaround; CI passed without that workaround. No workaround or warning suppression is committed.

Desktop resize follow-up: The reported SEH exception occurred in IDXGISwapChain4.ResizeBuffers. The previous fence was queued before Present. WaitIdle now signals and waits on a fresh queue fence. The sample resets its recording and releases its back-buffer owners before resizing. The WinForms timer pauses during rendering and stops on window close, and empty client rectangles are skipped.

CI passed at 151d941. The WARP test presented after both resizes (1024×720 → 1088×768 → 1024×720), rendered four frames, and exited successfully. The first fence-only attempt reproduced a later ResizeBuffers failure with E_ACCESSDENIED. The latest test covers the fence and window-loop changes together.

Remaining gates: interactive presentation, resize, and longer rendering soak runs on physical hardware. The original BasicSample CLR crash remains undiagnosed. See the architecture, ownership contract, coverage matrix and commands for the remaining port.

Consolidated by the preview 1 release in #9 and retained in main through #31. Verification: this PR head is an ancestor of release/automation at 1ba30ff4a36b6c4a7f8a31f342599026178c2cd0, whose tree 1c2649258445a6a22abeaa58cbc139c9384d0c5f exactly matches released main commit 0dcb5e3fbb984c23a1f313c87ec72ea0cbfe5fc4. Follow-up SDK work is tracked in #32–#35.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant