aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDuncan Sands <baldrick@free.fr>2007-09-26 16:24:52 +0000
committerDuncan Sands <baldrick@free.fr>2007-09-26 16:24:52 +0000
commit0869f4acec3b1b8b1c8d974a1fd7d0551284ae0c (patch)
treef0e951eda92da21b3d17c85b4fc2b4ad6dc88963
parentc90d68bf3d6b1c6fa7ca9fb09045a6e1a2e2cab4 (diff)
downloadexternal_llvm-0869f4acec3b1b8b1c8d974a1fd7d0551284ae0c.zip
external_llvm-0869f4acec3b1b8b1c8d974a1fd7d0551284ae0c.tar.gz
external_llvm-0869f4acec3b1b8b1c8d974a1fd7d0551284ae0c.tar.bz2
X86 -> X86-32 in appropriate places.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@42357 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--docs/ReleaseNotes.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html
index aa11404..917ca36 100644
--- a/docs/ReleaseNotes.html
+++ b/docs/ReleaseNotes.html
@@ -226,7 +226,7 @@ optimizer, speeding it up and making it more aggressive. For example:</p>
"restrict" pointer arguments to functions.</li>
<li>Duncan contributed support for trampolines (taking the address of a nested
- function). Currently this is only supported on the X86 target.</li>
+ function). Currently this is only supported on the X86-32 target.</li>
<li>Lauro Ramos Venancio contributed support to encode alignment info in
load and store instructions, the foundation for other alignment-related
@@ -529,7 +529,7 @@ bits.</p></li>
As in Algol and Pascal, lexical scoping of functions.
Nested functions are supported, but llvm-gcc does not support
- taking the address of a nested function (except on the X86 target)
+ taking the address of a nested function (except on the X86-32 target)
or non-local gotos.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
@@ -622,7 +622,7 @@ tested and works for a number of non-trivial programs, including LLVM
itself, Qt, Mozilla, etc.</p>
<ul>
-<li>Exception handling only works well on the linux/x86-32 target.
+<li>Exception handling only works well on the linux/X86-32 target.
In some cases, illegally throwing an exception does not result
in a call to terminate.</li>