commit 12881e79b60886df8872045044f34d4ab3d79535
author Duncan Sands <baldrick@free.fr> Mon Aug 30 10:57:54 2010 +0000
committer Duncan Sands <baldrick@free.fr> Mon Aug 30 10:57:54 2010 +0000
tree 4851aade4052bac15ec3cb8432109dc490180edb
parent cdd4f8c7cb0e5aa6e8d2b73f668c459936fe11d3

Remove a hack that tries to understand incorrect triples from the
Triple class constructor.  Only valid triples should now be used
inside LLVM - front-ends are now responsable for rejecting or
correcting invalid target triples.  The Triple::normalize method
can be used to straighten out funky triples provided by users.
Give this a whirl through the buildbots to see if I caught all
places where triples enter LLVM.


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

docs/ReleaseNotes.html

diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html
index f9f492c..b937f7d 100644
--- a/docs/ReleaseNotes.html
+++ b/docs/ReleaseNotes.html
@@ -348,6 +348,11 @@
   SMDiagnostic takes different parameters now. //FIXME: how to upgrade?
 </li>
 <li>
+  The constructor for the Triple class no longer tries to understand odd triple
+  specifications.  Frontends should ensure that they only pass valid triples to
+  LLVM.  The Triple::normalize utility method has been added to help front-ends
+  deal with funky triples.
+<li>
   Some APIs got renamed:
   <ul>
       <li>llvm_report_error -&gt; report_fatal_error</li>