[ace-users] Innacurate timers in Linux after 5.5.6

Thomas Girard thomas.g.girard at free.fr
Tue Jul 24 11:23:53 CDT 2007


On Tue, Jul 24, 2007 at 10:12:47AM -0500, Douglas C. Schmidt wrote:
> > On 7/24/07, Johnny Willemsen <jwillemsen at remedy.nl> wrote:
> > > The configure script does check a lot of defines, but it really isn't
> > > complete. A large amount of work has to be done to improve that support, but
> > > that will need funding. Probably something gets detected wrong and then in
> > > ACE_OS::gethrtime() the wrong code is triggered.
> > 
> > I recently rebuilt ACE using the configure script and found that the
> > resulting config.h had (mistakenly) decided that ACE_OS::fast_memcpy
> > was faster than ::memcpy (it isn't, by a factor of about 3) and that
> > my system had no SysV named semaphore operations (it does).
> > 
> > It seems that configure is definitely to be used with some care and
> > the resulting config.h should be carefully checked.
> Yes, indeed!  In general, the configure scripts need to be enhanced and
> tested carefully.  It would be great if someone(s) would like to
> volunteer to help with this effort and/or sponsor one of the commercial
> companies to do the work.

I've started providing experimental Debian packages using the configure
method. They seem to compile cleanly[1] on many arches, but I have not
carefully checked the generated config.h.

I'll try to find the bogus detection reported above. If I am successfull
in this I'll volunteer :)



[1] http://experimental.debian.net/build.php?pkg=ace

More information about the Ace-users mailing list