This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC-3.2.3 prerelease, 1st iteration
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- To: gcc at gcc dot gnu dot org
- Cc: ebotcazou at libertysurf dot fr
- Date: Tue, 15 Apr 2003 05:23:54 -0500 (CDT)
- Subject: Re: GCC-3.2.3 prerelease, 1st iteration
- Organization: Networks and Infrastructure Lab (IL02/2240), Motorola Labs
- References: <m3he93o939.fsf@uniton.integrable-solutions.net>
In article <200304151157 dot 55166 dot ebotcazou at libertysurf dot fr> you write:
> I think you didn't split correctly, it's
> WARNING: program timed out.
> FAIL: thread/pthread4.cc execution test
> I have seen this "problem" since I started testing on Sparc boxes (Ultra-2
> and Ultra-60).
Yes, as the author/installer of the test: It is probably harmless if
the test fails with the "program timed out" message before the FAIL.
It would be useful to check to see if it is "live/deadlocking", or
really just not completing all iterations within the dejagnu time limit.
Regards,
Loren