FA-52754 / Raster memory layout / Member archive

Split Depth Stencil Aspects: Depth plane origin uses no tag or stencil tag size · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at depth_origin.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

A toy depth-stencil image stores three depth bytes per texel in one plane and one stencil byte per texel in a second plane. Depth rows have one pad byte, stencil rows two; planes begin with distinct four- and six-byte tags. Return the named intermediate layout descriptor and final address fields; all quantities are integer byte offsets unless explicitly stated.

Why this case matters

Offline raster resource, upload, readback, and storage-layout regression model.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
layout fixture 1	`{"allocation_end": 57, "depth_address": 44, "depth_origin": 44, "depth_pitch": 4, "selected_address": 44, "selected_end": 47, "selected_width": 3, "stencil_address": 54, "stencil_origin": 54, "stencil_pitch": 3}`	`{"allocation_end": 61, "depth_address": 48, "depth_origin": 48, "depth_pitch": 4, "selected_address": 48, "selected_end": 51, "selected_width": 3, "stencil_address": 58, "stencil_origin": 58, "stencil_pitch": 3}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.