Reworking the wording of the "target data string" paragraph in the "Optimizer Improvments" section of the release notes.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@102059 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Wesley Peck 2010-04-22 13:28:34 +00:00
parent ed38745a2a
commit 68d1fe9700

View File

@ -544,11 +544,10 @@ href="http://blog.llvm.org/2009/12/introduction-to-load-elimination-in-gvn.html"
Advanced Topics in Redundant Load Elimination with a Focus on PHI Translation Advanced Topics in Redundant Load Elimination with a Focus on PHI Translation
Blog Post</a> for more details.</li> Blog Post</a> for more details.</li>
<li>The module <a href="LangRef.html#datalayout">target data string</a> now <li>The module <a href="LangRef.html#datalayout">target data string</a> now
includes a notion of what the 'native' integer data types a for the target, includes a notion of 'native' integer data types for the target. This
which allows various optimizations to use. This helps mid-level helps mid-level optimizations avoid promoting complex sequences of
optimizations avoid promoting complex sequences of operations to data types operations to data types that are not natively supported (e.g. converting
that are not natively supported (e.g. converting i32 operations to i64 on i32 operations to i64 on 32-bit chips).</li>
a 32-bit chip).</li>
<li>The mid-level optimizer is now conservative when operating on a module with <li>The mid-level optimizer is now conservative when operating on a module with
no target data. Previously, it would default to SparcV9 settings, which is no target data. Previously, it would default to SparcV9 settings, which is
not what most people expected.</li> not what most people expected.</li>