llvm.org GIT mirror llvm / 405ce8d
Update release document with more details. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@79818 91177308-0d34-0410-b5e6-96231b3b80d8 Tanya Lattner 11 years ago
1 changed file(s) with 24 addition(s) and 12 deletion(s). Raw diff Collapse all Expand all
201201 tar -czvf - llvm-X.X | gzip > llvm-X.X.tar.gz
202202 tar -czvf - llvm-test-X.X | gzip > llvm-test-X.X.tar.gz
203203 tar -czvf - llvm-gcc4.2-X.X.source | gzip > llvm-gcc-4.2-X.X.source.tar.gz
204 tar -czvf - clang-X.X.source | gzip > clang-X.X.source.tar.gz
204 tar -czvf - clang-X.X | gzip > clang-X.X.tar.gz
205205
206206
207207
212212
213213
214214 The build of llvm, llvm-gcc, and clang must be free
215 of errors and warnings in both debug and release modes. If both debug and
216 release builds are clean, then the release passes build qualification.
215 of errors and warnings in both debug, release, and release-asserts builds.
216 If all builds are clean, then the release passes build qualification.
217
218
219
  • debug: ENABLE_OPTIMIZED=0
  • 220
  • release: ENABLE_OPTIMIZED=1
  • 221
  • release-asserts: ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1
  • 222
    217223
    218224
    219225
    220226
    221227
    222228

    223 Build both debug and release (optimized) versions of LLVM on all supported
    224 platforms. Direction to build llvm are
    229 Build both debug, release (optimized), and release-asserts versions of
    230 LLVM on all supported platforms. Direction to build llvm are
    225231 here.
    226232

    227233
    238244
  • 239245 Build the LLVM GCC front-end by following the directions in the README.LLVM
    240246 file. The frontend must be compiled with c, c++, objc (mac only),
    241 objc++ (mac only) and fortran support.
    242 Be sure to build with LLVM_VERSION_INFO=X.X, where X is the major and
    247 objc++ (mac only) and fortran support.
    248
  • Please boostrap as well.
  • 249
  • Be sure to build with LLVM_VERSION_INFO=X.X, where X is the major and
  • 243250 minor release numbers.
    244251
    245252
    256263 Binary Distribution
    257264
    258265

    259 Creating the Clang binary distribution (release/optimized) requires
    266 Creating the Clang binary distribution (debug/release/release-asserts) requires
    260267 performing the following steps for each supported platform:
    261268

    262269
    290297
    ArchitectureOScompiler
    291298
    x86-32Mac OS 10.5gcc 4.0.1
    292299
    x86-32Linuxgcc 4.2.X, gcc 4.3.X
    293
    x86-32FreeBSDgcc ?
    294
    x86-32mingwgcc ?
    300
    x86-32FreeBSDgcc 4.2.X
    301
    x86-32mingwgcc 3.4.5
    295302
    x86-64Mac OS 10.5gcc 4.0.1
    296303
    x86-64Linuxgcc 4.2.X, gcc 4.3.X
    297
    x86-64FreeBSDgcc?
    304
    x86-64FreeBSDgcc 4.2.X
    298305
    299306
    300307

    310317 A release is qualified when it has no regressions from the previous 311318 release (or baseline). Regressions are related to correctness only and not 312319 performance at this time. Regressions are new failures in the set of tests that 313 are used to qualify each product and do not include anything not in the list. 320 are used to qualify each product and only include things on the list. 321 Ultimately, there is no end to the number of possible bugs in a release. We 322 need a very concrete and definitive release criteria that ensures we have 323 monotonically improving quality on some metric. The metric we use is 324 described below. This doesn't mean that we don't care about other things, 325 but this are things that must be satisfied before a release can go out 314326
    315327 316328