gcc:

	* doc/sourcebuild.texi (Effective-Target Keywords): Document
	run_expensive_tests.

	gcc/testsuite:
	* lib/target-supports.exp
	(check_effective_target_run_expensive_tests): New proc.
	* gcc.c-torture/compile/limits-fnargs.c: Use
	dg-require-effective-target run_expensive_tests.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@164012 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 3bf3885c4c6fc3d94f2a2069c78d0a824548a104..ec12d0533d8529aa6bfecc07e601ffb429e0ec06 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2010-09-08  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
+
+       * doc/sourcebuild.texi (Effective-Target Keywords): Document
+       run_expensive_tests.
+
 2010-09-08  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
 
        * toplev.c (output_stack_usage): Use lbasename instead of

diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi
index e7ff2928a9b9dc0cb88035fd894ec77d04edff86..83a0dbfab152b6e5b3b7b75613cc8a9dea9b284d 100644 (file)
--- a/gcc/doc/sourcebuild.texi
+++ b/gcc/doc/sourcebuild.texi
@@ -1680,6 +1680,11 @@ Target can compile using @code{pthread.h} with no errors or warnings.
 @item pthread_h
 Target has @code{pthread.h}.
 
+@item run_expensive_tests
+Expensive testcases (usually those that consume excessive amounts of CPU
+time) should be run on this target.  This can be enabled by setting the
+@env{GCC_TEST_RUN_EXPENSIVE} environment variable to a non-empty string.
+
 @item simulator
 Test system runs executables on a simulator (i.e. slowly) rather than
 hardware (i.e. fast).

diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index e5c116a97c7236644230e4bd1a8d9ff2efe3d006..f53301342982188df736981456abd5104b9e33b6 100644 (file)
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,10 @@
+2010-09-08  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
+
+       * lib/target-supports.exp
+       (check_effective_target_run_expensive_tests): New proc.
+       * gcc.c-torture/compile/limits-fnargs.c: Use
+       dg-require-effective-target run_expensive_tests.
+
 2010-09-08  Jakub Jelinek  <jakub@redhat.com>
 
        PR fortran/45597

diff --git a/gcc/testsuite/gcc.c-torture/compile/limits-fnargs.c b/gcc/testsuite/gcc.c-torture/compile/limits-fnargs.c
index 6640d1a7472d6cc1cd0be08cd88bd747cd8328f0..126a2b8e7d33618ecda019b234aee96f28c460f9 100644 (file)
--- a/gcc/testsuite/gcc.c-torture/compile/limits-fnargs.c
+++ b/gcc/testsuite/gcc.c-torture/compile/limits-fnargs.c
@@ -1,4 +1,5 @@
 /* { dg-timeout-factor 4.0 } */
+/* { dg-require-effective-target run_expensive_tests } */
 
 #define PAR1 int, int, int, int, int, int, int, int, int, int
 #define PAR2 PAR1, PAR1, PAR1, PAR1, PAR1, PAR1, PAR1, PAR1, PAR1, PAR1

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index 4b95323c96cc6986049145cad901b51fc3e78bdd..638c9eecd4124e54736e220a91036501c5a0b5d8 100644 (file)
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -3579,3 +3579,12 @@ proc check_effective_target_c++ { } {
     }
  return 0
 }
+
+# Return 1 if expensive testcases should be run.
+
+proc check_effective_target_run_expensive_tests { } {
+    if { [getenv GCC_TEST_RUN_EXPENSIVE] != "" } {
+        return 1
+    }
+    return 0
+}