This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

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: [PATCH] Re: Whats up with _POSIX_CPUTIME

From: Roland McGrath <roland at redhat dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Steve Munroe <sjmunroe at us dot ibm dot com>,libc-hacker at sources dot redhat dot com, dgm69 at us dot ibm dot com
Date: Wed, 1 Dec 2004 12:22:33 -0800
Subject: Re: [PATCH] Re: Whats up with _POSIX_CPUTIME

> On Wed, Dec 01, 2004 at 12:00:06PM -0800, Roland McGrath wrote:
> > > Did you just mean the s/#if #defined/#if defined/ in posix/tst-regex2.c?
> > > That's the only thing I found during testing...
> > 
> > That's the only thing I noticed, but it indicated the patch wasn't tested.
> > 
> > I don't like the __HAVE_CPUTIME stuff.  Already on ia64 it is a runtime
> > determination if the clocks are available.  
> 
> So should I redo that just to call __sysconf (_SC_{THREAD_,}CPUTIME)?

I think so, yes.  Or anyway, cope with runtime failures somehow.  I'd have
to look into the code closer to see if there is an obvious cheaper way to
catch it.

Follow-Ups:
- [PATCH] Re: Whats up with _POSIX_CPUTIME (take 2)
  - From: Jakub Jelinek

References:
- Re: [PATCH] Re: Whats up with _POSIX_CPUTIME
  - From: Jakub Jelinek

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