From: Duraid Madina <duraid@octopus.com.au>
Date: Sat, 14 May 2005 05:48:13 +0000 (+0000)
Subject: add a bit about the known problems on IA64
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;ds=sidebyside;h=2e36d6ecb41be03ddbd33101de82dc640045fd1c;p=oota-llvm.git

add a bit about the known problems on IA64


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@22003 91177308-0d34-0410-b5e6-96231b3b80d8
---

diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html
index 23aeda38d03..9bfac5c4552 100644
--- a/docs/ReleaseNotes.html
+++ b/docs/ReleaseNotes.html
@@ -597,6 +597,30 @@ frontends.</li>
 
 </div>
 
+<!-- ======================================================================= -->
+<div class="doc_subsection">
+  <a name="ia64-be">Known problems with the IA64 back-end</a>
+</div>
+
+<div class="doc_text">
+
+<ul>
+
+<li>C++ programs are likely to fail on IA64, as calls to <tt>setjmp</tt> are
+made where the argument is not 16-byte aligned, as required on IA64. (Strictly
+speaking this is not a bug in the IA64 back-end; it will also be encountered
+when building C++ programs using the C back-end.)</li>
+
+<li>There are a few ABI violations which will lead to problems
+when mixing LLVM output with code built with other compilers,
+particularly for C++ and floating-point programs.</li>
+
+<li>Vararg functions are not supported.</li>
+
+</ul>
+
+</div>
+
 <!-- *********************************************************************** -->
 <div class="doc_section">
   <a name="additionalinfo">Additional Information</a>