6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-08-05 13:26:55 +00:00
Code Issues Projects Releases Wiki Activity

Temporarily revert r61019, r61030, and r61040. These were breaking LLVM Release

Browse Source 
builds.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@61094 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Bill Wendling
2008-12-16 19:06:48 +00:00
parent 905ff1ebc4
commit 6fa311c233
10 changed files with 41 additions and 111 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/AliasAnalysis.html
View File

@@ -192,11 +192,11 @@ and returns MustAlias, MayAlias, or NoAlias as appropriate.
<div class="doc_text">
<p>The NoAlias response is used when the two pointers refer to distinct objects,
regardless of whether the pointers compare equal. For example, freed pointers
don't alias any pointers that were allocated afterwards. As a degenerate case,
pointers returned by malloc(0) have no bytes for an object, and are considered
NoAlias even when malloc returns the same pointer. The same rule applies to
NULL pointers.</p>
even regardless of whether the pointers compare equal. For example, freed
pointers don't alias any pointers that were allocated afterwards. As a
degenerate case, pointers returned by malloc(0) have no bytes for an object,
and are considered NoAlias even when malloc returns the same pointer. The same
rule applies to NULL pointers.</p>
<p>The MayAlias response is used whenever the two pointers might refer to the
same object. If the two memory objects overlap, but do not start at the same

12
docs/LangRef.html
View File

@@ -894,15 +894,9 @@ declare signext i8 @returns_signed_char()
parameter. The caller is responsible for ensuring that this is the
case. On a function return value, <tt>noalias</tt> additionally indicates
that the pointer does not alias any other pointers visible to the
caller. For further details, please see the discussion of the NoAlias
response in
<a href="http://llvm.org/docs/AliasAnalysis.html#MustMayNo">alias
analysis</a>.</dd>
<dt><tt>nocapture</tt></dt>
<dd>This indicates that the callee does not make any copies of the pointer
that outlive the callee itself. This is not a valid attribute for return
values.</dd>
caller. Note that this applies only to pointers that can be used to actually
load/store a value: NULL, unique pointers from malloc(0), and freed pointers
are considered to not alias anything.</dd>
<dt><tt>nest</tt></dt>
<dd>This indicates that the pointer parameter can be excised using the