mirror/gcc
2
0
Fork 0
mirror of git://gcc.gnu.org/git/gcc.git synced 2024-12-22 17:42:04 +08:00
Code Issues Packages Projects Releases Wiki Activity

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

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

From-SVN: r29018
This commit is contained in:
Jeffrey A Law 1999-08-31 23:59:40 +00:00 committed by Jeff Law
parent 61c48fbf26
commit a12e24fcb9
2 changed files with 20 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/testsuite/ChangeLog
View File

@ -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.

16
gcc/testsuite/lib/c-torture.exp
View File

@ -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;
}