This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/28614] gcc.c-torture/compile/20001226-1.c times out
- From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Dec 2008 20:42:23 -0000
- Subject: [Bug other/28614] gcc.c-torture/compile/20001226-1.c times out
- References: <bug-28614-276@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from dave at hiauly1 dot hia dot nrc dot ca 2008-12-05 20:42 -------
Subject: Re: gcc.c-torture/compile/20001226-1.c times out
> ------- Comment #3 from sje at cup dot hp dot com 2008-12-05 17:16 -------
> Dave, I added a dg-timeout-factor to this test for HPPA so it shouldn't time
> out on PA boxes anymore. I hadn't noticed the x86 timeout part of the report
> when I first looked at it. Do you still have that problem? If so we can
> change the test to increase the timeout there too or, if you don't have that
> problem anymore we can just close this bug out since it should be fixed on PA
> now.
I haven't done a GCC build recently on this x86 system but I don't
believe there is a timeout problem with this test on most x86 systems.
Instead of just arbitrarily increasing the timeout values, I tend to think
timeout values should be scaled based on the time for some base compilation.
It also would be nice to keep execution time records for certain benchmark
tests to that it might be possible to detect regressions in compilation
speed.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28614