From 8246adc1f0e2d28374da3aeab864aee5ff03f3ff Mon Sep 17 00:00:00 2001 From: Duncan Sands Date: Wed, 7 Jul 2010 07:48:00 +0000 Subject: Rename "Release" builds as "Release+Asserts"; rename "Release-Asserts" builds to "Release". The default build is unchanged (optimization on, assertions on), however it is now called Release+Asserts. The intent is that future LLVM releases released via llvm.org will be Release builds in the new sense, i.e. will have assertions disabled (currently they have assertions enabled, for a more than 20% slowdown). This will bring them in line with MacOS releases, which ship with assertions disabled. It also means that "Release" now means the same things in make and cmake builds: cmake already disables assertions for "Release" builds AFAICS. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@107758 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/HowToReleaseLLVM.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'docs/HowToReleaseLLVM.html') diff --git a/docs/HowToReleaseLLVM.html b/docs/HowToReleaseLLVM.html index c0ad6c9381..933b158793 100644 --- a/docs/HowToReleaseLLVM.html +++ b/docs/HowToReleaseLLVM.html @@ -213,13 +213,13 @@ Building the Release
The build of llvm, llvm-gcc, and clang must be free -of errors and warnings in both debug, release, and release-asserts builds. +of errors and warnings in both debug, release+asserts, and release builds. If all builds are clean, then the release passes build qualification.
  1. debug: ENABLE_OPTIMIZED=0
  2. -
  3. release: ENABLE_OPTIMIZED=1
  4. -
  5. release-asserts: ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1
  6. +
  7. release+asserts: ENABLE_OPTIMIZED=1
  8. +
  9. release: ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1
@@ -227,7 +227,7 @@ If all builds are clean, then the release passes build qualification.
Build LLVM

- Build both debug, release (optimized), and release-asserts versions of + Build both debug, release+asserts (optimized), and release versions of LLVM on all supported platforms. Direction to build llvm are here.

@@ -264,7 +264,7 @@ If all builds are clean, then the release passes build qualification. Binary Distribution

- Creating the Clang binary distribution (debug/release/release-asserts) requires + Creating the Clang binary distribution (debug/release/release) requires performing the following steps for each supported platform:

@@ -429,7 +429,7 @@ Qualification Details

- The final stages of the release process involving taging the release branch, + The final stages of the release process involving tagging the release branch, updating documentation that refers to the release, and updating the demo page.

FIXME: Add a note if anything needs to be done to the clang website. -- cgit v1.2.3