From f08c5d87d0e078ae107c8994c8ebe00214cfb368 Mon Sep 17 00:00:00 2001 From: John Criswell Date: Fri, 24 Oct 2003 22:48:20 +0000 Subject: [PATCH] Added answers to test suite questions. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9501 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/FAQ.html | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/docs/FAQ.html b/docs/FAQ.html index a76fea66f69..3ada460b03f 100644 --- a/docs/FAQ.html +++ b/docs/FAQ.html @@ -138,8 +138,39 @@ LLVM: Frequently Asked Questions cases, this takes care of the problem. To do this, just type make clean and then make in the directory that fails to build.

+ +

I've built LLVM and am testing it, but the tests freeze. +
+ This is most likely occurring because you built a profile or release + (optimized) build of LLVM and have not specified the same information on + the gmake command line. +

+ For example, if you built LLVM with the command: +

+ gmake ENABLE_PROFILING=1 +

+ ...then you must run the tests with the following commands: +

+ cd llvm/test
gmake ENABLE_PROFILING=1 +

+ +

Why do test results differ when I perform different types of + builds? +
+ The LLVM test suite is dependent upon several features of the LLVM tools + and libraries. +

+ First, the debugging assertions in code are not enabled in optimized or + profiling builds. Hence, tests that used to fail may pass. +

+ Second, some tests may rely upon debugging options or behavior that is + only available in the debug build. These tests will fail in an optimized + or profile build.

+The LLVM Compiler Infrastructure +
+ -- 2.34.1