summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDavid Greene <greened@obbligato.org>2011-10-19 13:04:56 +0000
committerDavid Greene <greened@obbligato.org>2011-10-19 13:04:56 +0000
commite7c3ea9704be2f4ee9daca2336133a4adb90de37 (patch)
tree0bcec62825138ee312948df0a27f3cbf7942f22d
parent13c8360c2690f2fa6ccfdbf31a87614e245b1887 (diff)
downloadbcm5719-llvm-e7c3ea9704be2f4ee9daca2336133a4adb90de37.tar.gz
bcm5719-llvm-e7c3ea9704be2f4ee9daca2336133a4adb90de37.zip
Document NAME
Document NAME as a special member of def records that should not be defined anywhere else. llvm-svn: 142527
-rw-r--r--llvm/docs/TableGenFundamentals.html8
1 files changed, 8 insertions, 0 deletions
diff --git a/llvm/docs/TableGenFundamentals.html b/llvm/docs/TableGenFundamentals.html
index e8fca325130..f7f3d97ffe9 100644
--- a/llvm/docs/TableGenFundamentals.html
+++ b/llvm/docs/TableGenFundamentals.html
@@ -207,6 +207,14 @@ file, to factor out the common features that instructions of its class share. A
key feature of TableGen is that it allows the end-user to define the
abstractions they prefer to use when describing their information.</p>
+<p>Each def record has a special entry called "NAME." This is the
+name of the def ("ADD32rr" above). In the general case def names can
+be formed from various kinds of string processing expressions and NAME
+resolves to the final value obtained after resolving all of those
+expressions. The user may refer to NAME anywhere she desires to use
+the ultimate name of the def. NAME should not be defined anywhere
+else in user code to avoid conflict problems.</p>
+
</div>
<!-- ======================================================================= -->
OpenPOWER on IntegriCloud