From 2fd297703c3f47a2c48140767efb738fe96d3e13 Mon Sep 17 00:00:00 2001 From: Anupama Chandrasekhar Date: Mon, 21 Oct 2024 14:10:46 -0700 Subject: [PATCH] Minor update to optional attribute section --- proposals/NNNN-max-records-per-node.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/proposals/NNNN-max-records-per-node.md b/proposals/NNNN-max-records-per-node.md index 437f4175..06647bc4 100644 --- a/proposals/NNNN-max-records-per-node.md +++ b/proposals/NNNN-max-records-per-node.md @@ -108,8 +108,9 @@ they are different. We therefore prefer the option of specifying `MaxRecordsPerN ### Optional Attribute This attribute could be made optional, for maximum backward compatibility; i.e. existing SM6.8 Work Graphs compile with -the newer Shader Model. When `MaxRecordsPerNode` is _not_ specified, the implicit value of `MaxRecordsPerNode` is equal -to `MaxRecords`. This also avoids redundant attribute specifications for those usage models where the values of -`MaxRecords` and `MaxRecordsPerNode` are identical. +the newer Shader Model. When `MaxRecordsPerNode` is _not_ specified, the implicit value of `MaxRecordsPerNode` is +equal to `MaxRecords`. This also avoids redundant attribute specifications for those usage models where the values of +`MaxRecords` and `MaxRecordsPerNode` are identical. However, for performance reasons, this was made a required +attribute with a compiler fall back for backward compatibilty.