Commit 5230fa04 authored by Ben Gamari's avatar Ben Gamari Committed by Ben Gamari

validate: Add --build-only

This will allow us to split up Harbormaster output for the build and
test stages of validation.

Test Plan: `./validate --build-only && ./validate --testsuite-only`

Reviewers: thomie, hvr, austin

Differential Revision: https://phabricator.haskell.org/D2553

(cherry picked from commit 4d2b15d5)
parent c93ad554
......@@ -14,6 +14,7 @@ Flags:
--no-clean don't make clean first, just carry on from
a previous interrupted validation run
--testsuite-only don't build the compiler, just run the test suite
--build-only don't test the compiler, just build it
--hpc build stage2 with -fhpc, and see how much of the
compiler the test suite covers.
2008-07-01: 63% slower than the default.
......@@ -46,6 +47,7 @@ EOF
no_clean=0
testsuite_only=0
build_only=0
hpc=NO
speed=NORMAL
use_dph=0
......@@ -64,6 +66,9 @@ do
--testsuite-only)
testsuite_only=1
;;
--build-only)
build_only=1
;;
--hpc)
hpc=YES
;;
......@@ -240,6 +245,16 @@ fi # testsuite-only
# -----------------------------------------------------------------------------
# Run the testsuite
if [ "$build_only" -eq 1 ]; then
cat <<EOF
-------------------------------------------------------------------
Congratulations! This tree has compiled successfully.
You can now test your new compiler using ./validate --testsuite-only.
EOF
exit 0
fi
if [ "$hpc" = YES ]
then
# XXX With threads we'd need to give a different tix file to each thread
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment