Re: [Valgrind-developers] semaphores - remapping and corrected sem_destroy

[Tom H. <th...@cy...>]

In message <108...@as...>
          Aleksander Salwa <A....@os...> wrote:

> It removes VG_N_SEMAPHORES limitation.
> Now it uses malloc/free for each sem_init/sem_destroy, as Jeremy
> suggested. I've done some benchmarking - it works even faster than my
> previous version (with pointers to a big global table). It shows again
> that "programmers are notoriously bad at predicting how their programs
> actually perform", as GCC's manual says ;-)
> 
> Could someone with write access do a "cvs ci" ?

Looks good to me, so I've added a test case and committed it. Thanks
for the patch.

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/