replica
/
hanchenye-llvm-project
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

llvm-svn: 102059
This commit is contained in:
Wesley Peck 2010-04-22 13:28:34 +00:00
parent d80517c061
commit c845916929
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
llvm/docs/ReleaseNotes.html
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
Blog Post</a> for more details.</li>
<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,
which allows various optimizations to use. This helps mid-level
optimizations avoid promoting complex sequences of operations to data types
that are not natively supported (e.g. converting i32 operations to i64 on
a 32-bit chip).</li>
includes a notion of 'native' integer data types for the target. This
helps mid-level optimizations avoid promoting complex sequences of
operations to data types that are not natively supported (e.g. converting
i32 operations to i64 on 32-bit chips).</li>
<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
not what most people expected.</li>