summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDan Gohman <gohman@apple.com>2010-05-03 14:58:14 +0000
committerDan Gohman <gohman@apple.com>2010-05-03 14:58:14 +0000
commita9601bb6fbe7ddfa979fdaaa3130ea12ab8ac4a5 (patch)
treece11292ad7e31a2f5518350de70003a2fd4214e8
parent7292a759b4215bbf7e803e016ef6055bcf40cfda (diff)
downloadbcm5719-llvm-a9601bb6fbe7ddfa979fdaaa3130ea12ab8ac4a5.tar.gz
bcm5719-llvm-a9601bb6fbe7ddfa979fdaaa3130ea12ab8ac4a5.zip
Delete this comment. The behavior of struct loads and stores with
respect to padding bytes isn't something that the dependence text needs to spell out. llvm-svn: 102910
-rw-r--r--llvm/docs/LangRef.html2
1 files changed, 0 insertions, 2 deletions
diff --git a/llvm/docs/LangRef.html b/llvm/docs/LangRef.html
index 4904fd9155f..9294d36c6c2 100644
--- a/llvm/docs/LangRef.html
+++ b/llvm/docs/LangRef.html
@@ -2367,8 +2367,6 @@ has undefined behavior.</p>
(including loads and stores implied by intrinsics such as
<a href="#int_memcpy"><tt>@llvm.memcpy</tt></a>.)</li>
-<!-- FIXME: padding in the middle of a struct -->
-
<!-- TODO: In the case of multiple threads, this only applies to loads and
stores from the same thread as the store, or which are sequenced after the
store by synchronization. -->
OpenPOWER on IntegriCloud