6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-01-29 13:32:33 +00:00
Code Issues Projects Releases Wiki Activity

Added answers to test suite questions.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9501 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
John Criswell 2003-10-24 22:48:20 +00:00
parent 8fc493430c
commit f08c5d87d0
1 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
docs/FAQ.html
View File

@ -138,8 +138,39 @@ LLVM: Frequently Asked Questions
cases, this takes care of the problem. To do this, just type <tt>make
clean</tt> and then <tt>make</tt> in the directory that fails to build.
<p>
<dt><b>I've built LLVM and am testing it, but the tests freeze.</b>
<dd>
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 <tt>gmake</tt> command line.
<p>
For example, if you built LLVM with the command:
<p>
<tt>gmake ENABLE_PROFILING=1</tt>
<p>
...then you must run the tests with the following commands:
<p>
<tt>cd llvm/test<br>gmake ENABLE_PROFILING=1</tt>
<p>
<dt><b>Why do test results differ when I perform different types of
builds?</b>
<dd>
The LLVM test suite is dependent upon several features of the LLVM tools
and libraries.
<p>
First, the debugging assertions in code are not enabled in optimized or
profiling builds. Hence, tests that used to fail may pass.
<p>
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.
</dl>
<hr>
<a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a>
<br>
</body>
</html>