[Valgrind-developers] 2008-01-17 03:05:04 GMT nightly build (lloyd, x86_64, Fedora 7)

Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2008-01-17 03:05:04 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ...

[Valgrind-developers] 2008-01-17 03:15:04 GMT nightly build (alvis, i686, Red Hat 7.3)

Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2008-01-17 03:15:04 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ..

[Valgrind-developers] 2008-01-17 03:10:06 GMT nightly build (dellow, x86_64, Fedora 8)

Nightly build on dellow ( x86_64, Fedora 8 ) started at 2008-01-17 03:10:06 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ..

[Valgrind-developers] 2008-01-17 03:00:03 GMT nightly build (gill, x86_64, Fedora Core 2)

Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2008-01-17 03:00:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests

Re: [Valgrind-developers] Some changes and additional tests for helgrind.

Great! Do you plan to checkin these or similar changes in future? Maybe under #ifdef so that users do not suffer if they don't need too many [TL]SETs? While I think that something like 24 bits for [TL]SETs is a must for large apps, it might not be enough. We may need some garbage collection for [T