RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-12-02 08:46:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clarify that the rules about object hopping kick in when a pointer is

Browse Source 
deferenced, rather than when the pointer value is computed.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@96596 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Dan Gohman 2010-02-18 18:22:18 +00:00
parent cf3d08445d
commit 48f6a3175a
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/AdvancedGetElementPtr.html
View File

@ -44,10 +44,10 @@
where it doesn't do this. With GEP you can avoid this problem.
<p>Also, GEP carries additional pointer aliasing rules. It's invalid to take a
GEP from one object and address into a different separately allocated
object. IR producers (front-ends) must follow this rule, and consumers
(optimizers, specifically alias analysis) benefit from being able to rely
on it.</p>
GEP from one object, address into a different separately allocated
object, and deference it. IR producers (front-ends) must follow this rule,
and consumers (optimizers, specifically alias analysis) benefit from being
able to rely on it.</p>
<p>And, GEP is more concise in common cases.</p>