* 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
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
basename.
@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).
+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
/* { 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
}
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
+}