Accidental enable of bad code

[oota-llvm.git] / docs / HowToSubmitABug.html

diff --git a/docs/HowToSubmitABug.html b/docs/HowToSubmitABug.html
index 7bc6414a5dccfe58d64306bae2b0f3561816a5e9..f01c5c72a10064052668051dbb11722a764f5589 100644 (file)
--- a/docs/HowToSubmitABug.html
+++ b/docs/HowToSubmitABug.html
@@ -57,7 +57,7 @@ down the bug so that the person who fixes it will be able to find the problem
 more easily.</p>
 
 <p>Once you have a reduced test-case, go to <a
-href="http://llvm.cs.uiuc.edu/bugs/enter_bug.cgi">the LLVM Bug Tracking
+href="http://llvm.org/bugs/enter_bug.cgi">the LLVM Bug Tracking
 System</a>, select the category in which the bug falls, and fill out the form
 with the necessary details.  The bug description should contain the following
 information:</p>
@@ -82,8 +82,8 @@ information:</p>
 <div class="doc_text">
 
 <p>More often than not, bugs in the compiler cause it to crash - often due to an
-assertion failure of some sort.  If you are running <tt><b>opt</b></tt> or
-<tt><b>analyze</b></tt> directly, and something crashes, jump to the section on
+assertion failure of some sort.  If you are running <tt><b>opt</b></tt> 
+directly, and something crashes, jump to the section on
 <a href="#passes">bugs in LLVM passes</a>.  Otherwise, the most important
 piece of the puzzle is to figure out if it is the GCC-based front-end that is
 buggy or if it's one of the LLVM tools that has problems.</p>
@@ -350,7 +350,7 @@ the following:</p>
   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
 
   <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
-  <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a>
+  <a href="http://llvm.org">The LLVM Compiler Infrastructure</a>
   <br>
   Last modified: $Date$
 </address>