This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Recent 4.1 breakage...


Paolo wrote:
> I understand the regressions appeared between May 15 and May 17?!? In 
> that case, a quick look at the Changelog reveals that you should 
> definitely ping the compiler people!

Actually, I have now discounted that by looking at the 4.1 patch
applied between the dates and the failure mode.  Appears to be a host
semaphore issue (in particular, my machine has zero left ;-).

then:
> therefore seems an hard to reproduce long-standing problem, after all... 
> You can try whether backporting this patch from mainline helps:

> 2006-03-12  Howard Hinnant  <hhinnant@apple.com>
> (not sure if it qualifies for the branch...)

Agreed on the final point.

Regarding the first point: what appears to have happened on my machine
is that some test (or multiple tests) obtains an semaphore from the
system but doesn't always release it.  My machine is configured with
10 semaphores.  After running the test suite N times, they were exhausted.

Regards,
Loren


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]