summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorYong He <yonghe@outlook.com>2023-02-11 13:20:37 -0800
committerGitHub <noreply@github.com>2023-02-11 13:20:37 -0800
commit5bab4ead221b9e7637b541e9a35687aa990e8599 (patch)
tree849326d15515ecca3d8d34eb2ec0307a84cc3d5c /docs
parent82c7c780a6b0b8d728fdf9f2df2d820a78617e5b (diff)
Update 07-autodiff.md
Diffstat (limited to 'docs')
-rw-r--r--docs/user-guide/07-autodiff.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/user-guide/07-autodiff.md b/docs/user-guide/07-autodiff.md
index ddd4fe342..ad031bc07 100644
--- a/docs/user-guide/07-autodiff.md
+++ b/docs/user-guide/07-autodiff.md
@@ -567,6 +567,6 @@ The compiler can generate forward derivative and backward propagation implementa
- No access to global variables or shader parameters within a differentiable function.
- All operations to global resources, including texture reads or atomic writes, are treating as a non-differentiable operation.
- If a differentiable function contains calls that cause side-effects such as updates to global memory, there will not be a guarantee on how many times the side-effect will occur during the resulting derivative function or back-propagation function.
-- Loops: In a backward differentiable function, loops currently cannot have `continue` statements although `break` statements are supported. Loops must use the attribute `[MaxIters(<count>)]` to specify a maximum number of iterations. This will be used by compiler to allocate space to store intermediate data. If the actual number of iterations exceeds the provided maximum, the behavior is undefined. You can always mark loops with the `[ForceUnroll]` attribute to instruct the Slang compiler to unroll the loop before generating derivative propagation functions. Unrolled loops will be treated the same way as ordinary code and is not subject to any additional restrictions.
+- Loops: In a backward differentiable function, loops currently cannot have `continue` statements although `break` statements are supported. Loops must use the attribute `[MaxIters(<count>)]` to specify a maximum number of iterations. This will be used by compiler to allocate space to store intermediate data. If the actual number of iterations exceeds the provided maximum, the behavior is undefined. You can always mark a loop with the `[ForceUnroll]` attribute to instruct the Slang compiler to unroll the loop before generating derivative propagation functions. Unrolled loops will be treated the same way as ordinary code and are not subject to any additional restrictions.
The above restrictions do not apply if a user-defined derivative or backward propagation function is provided.