[llvm-commits] [llvm] r102059 - /llvm/trunk/docs/ReleaseNotes.html

[Wesley Peck]

Author: peckw
Date: Thu Apr 22 08:28:34 2010
New Revision: 102059

URL: http://llvm.org/viewvc/llvm-project?rev=102059&view=rev
Log:
Reworking the wording of the "target data string" paragraph in the "Optimizer Improvments" section of the release notes.

Modified:
    llvm/trunk/docs/ReleaseNotes.html

Modified: llvm/trunk/docs/ReleaseNotes.html
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/ReleaseNotes.html?rev=102059&r1=102058&r2=102059&view=diff
==============================================================================
--- llvm/trunk/docs/ReleaseNotes.html (original)
+++ llvm/trunk/docs/ReleaseNotes.html Thu Apr 22 08:28:34 2010
@@ -544,11 +544,10 @@
  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>