summaryrefslogtreecommitdiff
path: root/docs/user-guide/09-targets.md
diff options
context:
space:
mode:
authorYong He <yonghe@outlook.com>2024-02-27 13:32:43 -0800
committerGitHub <noreply@github.com>2024-02-27 13:32:43 -0800
commit1e5d0b31d28bdbf0d220c89debe5f9cc6b82a6fa (patch)
tree930282d397bf76b3c7fc6a77a8fa35d8916d48e0 /docs/user-guide/09-targets.md
parent92cc3a715d7fdbc460464a202ab404f8bd4e570c (diff)
Add documentation for link-time specialization. (#3638)
Diffstat (limited to 'docs/user-guide/09-targets.md')
-rw-r--r--docs/user-guide/09-targets.md2
1 files changed, 0 insertions, 2 deletions
diff --git a/docs/user-guide/09-targets.md b/docs/user-guide/09-targets.md
index d6dfd4cf6..0b7845108 100644
--- a/docs/user-guide/09-targets.md
+++ b/docs/user-guide/09-targets.md
@@ -363,5 +363,3 @@ Summary
This chapter has reviewed the main target platforms supported by the Slang compiler and runtime system.
A key point to take away is that there is great variation in the capabilities of these systems.
Even superficially similar graphics APIs have complicated differences in their parameter-passing mechanisms that must be accounted for by application programmers and GPU compilers.
-
-In the next chapter, we will discuss how the Slang compiler adapts to the different capabilities and rules of these platforms when laying out shader parameters in memory and then binding those parameters to the mechanisms defined by each platform.