From d465126f5d4c61318158876ead3e5b7309c8a0e5 Mon Sep 17 00:00:00 2001
From: Chris Lattner <sabre@nondot.org>
Date: Tue, 21 Mar 2006 01:10:57 +0000
Subject: [PATCH] Document ENABLE_ASSERTIONS=1

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@26915 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/GettingStarted.html | 5 +++++
 docs/MakefileGuide.html  | 4 ++++
 2 files changed, 9 insertions(+)

diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html
index a7c1819b452..d0a48e09072 100644
--- a/docs/GettingStarted.html
+++ b/docs/GettingStarted.html
@@ -955,6 +955,11 @@ declaring variables on the command line.  The following are some examples:</p>
   Perform a Release (Optimized) build.
   <p>
 
+  <dt><tt>gmake ENABLE_OPTIMIZED=1 ENABLE_ASSERTIONS=1</tt>
+  <dd>
+  Perform a Release (Optimized) build with assertions enabled.
+  <p>
+
   <dt><tt>gmake ENABLE_PROFILING=1</tt>
   <dd>
   Perform a Profiling build.
diff --git a/docs/MakefileGuide.html b/docs/MakefileGuide.html
index f1c546c80ce..254f21c9e2e 100644
--- a/docs/MakefileGuide.html
+++ b/docs/MakefileGuide.html
@@ -632,6 +632,10 @@
     to the compilers and linkers to ensure that profile data can be collected
     from the tools built. Use the <tt>gprof</tt> tool to analyze the output from
     the profiled tools (<tt>gmon.out</tt>).</dd>
+    <dt><a name="ENABLE_ASSERTIONS"><tt>ENABLE_ASSERTIONS</tt></a></dt>
+    <dd>If set to any value, causes the build to enable assertions, even if 
+    building a release or profile build.  This is slower than a release build but
+    far faster than a debug build.</dd>
     <dt><a name="EXPERIMENTAL_DIRS"><tt>EXPERIMENTAL_DIRS</tt></a></dt>
     <dd>Specify a set of directories that should be built, but if they fail, it
     should not cause the build to fail. Note that this should only be used