[NFC] Update release notes for 1.9.2607#8621
Conversation
…cs fix) Follow-up pass on the release notes after microsoft#8607: microsoft#8600 landed a general DXIL codegen fix that stops emitting illegal *.with.overflow intrinsics, which caused validation failures for overflow-check idioms when optimizations were enabled. Add it to the Upcoming Release bug fixes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 086148ba-a82b-41c4-8fa0-5eb63e5797e2
…rosoft#8608) Since this PR targets main, include the SM 6.10 experimental LinAlg validation changes merged since microsoft#8607: parameter/K-dimension validation (microsoft#8588) and restricting allowed matrix component types (microsoft#8608). The release branch caps SM to 6.9 and strips these separately. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 086148ba-a82b-41c4-8fa0-5eb63e5797e2
alsepkow
changed the title
| [#8271](https://github.com/microsoft/DirectXShaderCompiler/issues/8271). | ||
| - Corrected the parameter order of `InterlockedAccumulate` | ||
| [#8459](https://github.com/microsoft/DirectXShaderCompiler/pull/8459). | ||
| - Added validation of LinAlg matrix builtin parameters and result K dimension |
There was a problem hiding this comment.
If we're going with "This 1.9.2607 release will not be able to target SM 6.10", then shouldn't we leave / cut out this experimental shader model 6.10 section entirely? Users of this release won't be able to see / apply these release notes, right?
There was a problem hiding this comment.
We wont be including 6.10 support. I intend to remove the 6.10 features from the notes in the release branch after we cherry-pick them. And on main I'll label this section with the release title and move the 6.10 related things into the new upcoming release section that I'll add on main.
There was a problem hiding this comment.
On second thought, I'm going to remove these and label the section. That way we can have a single cherry-pick of the release notes into the release branch. And then a subsequent PR into main can add them back in under a new 'upcoming release' section.
bob80905
left a comment
bob80905
left a comment
There was a problem hiding this comment.
Approving because its possible we could leave the 6.10 notes in there, even though they're not accessible, yet it does properly describe the internal inaccessible changes in the new compiler.
…otes Rename the Upcoming Release section to Version 1.9.2607 (matching prior release sections) and remove the experimental Shader Model 6.10 content, so this can go cleanly to the 1.9 release branch. The 6.10 items will be re-added to a new Upcoming Release section in a follow-up PR. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 086148ba-a82b-41c4-8fa0-5eb63e5797e2
2 participants
Follow-up pass on the release notes after #8607, covering user-visible changes merged since.