c-torture.exp: Avoid the "compare executables" optimization when testing native.

        * lib/c-torture.exp: Avoid the "compare executables" optimization
        when testing native.

From-SVN: r29018

diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index e4163b4f625ec9a98f6e20d9854ab7e2115d3bf7..86d45e8de201432ad57e989fc0768a8ae2068b0a 100644 (file)
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,8 @@
+Tue Aug 31 17:57:49 1999  Jeffrey A Law  (law@cygnus.com)
+
+       * lib/c-torture.exp: Avoid the "compare executables" optimization
+       when testing native.
+
 Sun Aug 29 14:35:41 1999  Jeffrey A Law  (law@cygnus.com)
 
        * gcc.c-torture/execute/990829-1.c: New test.

diff --git a/gcc/testsuite/lib/c-torture.exp b/gcc/testsuite/lib/c-torture.exp
index 839c32caa80e25b77a7b053214b2c8e36f3f7cce..0c8aeda6106799bf80f185ffab74bf53a4d2bf97 100644 (file)
--- a/gcc/testsuite/lib/c-torture.exp
+++ b/gcc/testsuite/lib/c-torture.exp
@@ -189,8 +189,22 @@ proc c-torture-execute { src args } {
             set ignore_me [eval $torture_eval_before_execute]
        }
        
+
+       # Sometimes we end up creating identical executables for two
+       # consecutive sets of different of compiler options.
+       #
+       # In such cases we know the result of this test will be identical
+       # to the result of the last test.
+       #
+       # So in cases where the time to load and run/simulate the test
+       # is relatively high, compare the two binaries and avoid rerunning
+       # tests if the executables are identical.
+       #
+       # Do not do this for native testing since the cost to load/execute
+       # the test is fairly small and the comparison step actually slows
+       # the entire process down because it usually does not "hit".
        set skip 0;
-       if [info exists oldexec] {
+       if { ![isnative] && [info exists oldexec] } {
            if { [remote_file build cmp $oldexec $execname] == 0 } {
                set skip 1;
            }