From a6094be53321bf974903263743425622738c0995 Mon Sep 17 00:00:00 2001
From: Anton Korobeynikov
Date: Sun, 8 Jun 2008 10:24:13 +0000
Subject: [PATCH] Add win64
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@52091 91177308-0d34-0410-b5e6-96231b3b80d8
---
docs/ReleaseNotes.html | 23 ++++++++++++++++-------
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html
index e72f61ffe4b..82ba0c74b7e 100644
--- a/docs/ReleaseNotes.html
+++ b/docs/ReleaseNotes.html
@@ -306,17 +306,20 @@ faster:
area of passing and returning structures by value. llvm-gcc compiled code
now interoperates very well on X86-64 systems with other compilers.
+Support for Win64 was added. This includes codegeneration itself, JIT
+ support and necessary changes to llvm-gcc.
+
The LLVM X86 backend now supports the support SSE 4.1 instruction set, and
the llvm-gcc 4.2 front-end supports the SSE 4.1 compiler builtins. Various
generic vector operations (insert/extract/shuffle) are much more efficient
when SSE 4.1 is enabled. The JIT automatically takes advantage of these
instructions, but llvm-gcc must be explicitly told to use them, e.g. with
-march=penryn.
-
+
The X86 backend now does a number of optimizations that aim to avoid
converting numbers back and forth from SSE registers to the X87 floating
point stack.
-
+
The X86 backend supports stack realignment, which is particularly useful for
vector code on OS's without 16-byte aligned stacks.
@@ -326,7 +329,7 @@ faster:
Trampolines (taking the address of a nested function) now work on
Linux/x86-64.
-
+
__builtin_prefetch is now compiled into the appropriate prefetch
instructions instead of being ignored.
@@ -450,11 +453,17 @@ href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list.
-- The X86 backend does not yet support all inline assembly that uses the X86 floating
- point stack. It supports the 'f' and 't' constraints, but not 'u'.
-- The X86 backend generates inefficient floating point code when configured to
+
- The X86 backend does not yet support
+ all inline assembly that uses the X86
+ floating point stack. It supports the 'f' and 't' constraints, but not
+ 'u'.
+ - The X86 backend generates inefficient floating point code when configured to
generate code for systems that don't have SSE2.
+ - Win64 codegeneration wasn't widely tested. Everything should work, but we
+ expect small issues to happen. Also, llvm-gcc cannot build mingw64 runtime
+ currently due
+ to several
+ bugs in FP stackifier