From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Steve Munroe <sjmunroe@us.ibm.com>,
libc-hacker@sources.redhat.com, dgm69@us.ibm.com
Subject: Re: [PATCH] Re: Whats up with _POSIX_CPUTIME
Date: Wed, 01 Dec 2004 20:22:00 -0000 [thread overview]
Message-ID: <200412012022.iB1KMXkf012280@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Wednesday, 1 December 2004 21:20:17 +0100 <20041201202017.GN8259@sunsite.mff.cuni.cz>
> 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.
next prev parent reply other threads:[~2004-12-01 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 20:16 Steve Munroe
2004-11-30 20:42 ` Jakub Jelinek
2004-11-30 22:21 ` Roland McGrath
2004-11-30 23:35 ` [PATCH] " Jakub Jelinek
2004-12-01 0:08 ` Roland McGrath
2004-12-01 10:42 ` Jakub Jelinek
2004-12-01 20:00 ` Roland McGrath
2004-12-01 20:20 ` Jakub Jelinek
2004-12-01 20:22 ` Roland McGrath [this message]
2004-12-01 21:11 ` [PATCH] Re: Whats up with _POSIX_CPUTIME (take 2) Jakub Jelinek
2004-11-30 22:20 ` Whats up with _POSIX_CPUTIME Roland McGrath
2004-12-01 0:00 ` Steve Munroe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200412012022.iB1KMXkf012280@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=dgm69@us.ibm.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=sjmunroe@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).