From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eliz@gnu.org
Cc: nickrob@snap.net.nz, gdb-patches@sourceware.org
Subject: Re: [PATCH] MI: new timing command
Date: Sun, 31 Dec 2006 11:58:00 -0000 [thread overview]
Message-ID: <200612311158.kBVBw8x6021147@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <umz541yqg.fsf@gnu.org> (message from Eli Zaretskii on Sun, 31 Dec 2006 06:21:59 +0200)
> Date: Sun, 31 Dec 2006 06:21:59 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: Nick Roberts <nickrob@snap.net.nz>
> > Date: Sun, 31 Dec 2006 11:05:35 +1300
> > Cc: gdb-patches@sourceware.org
> >
> > > > diff -c -p -r1.86 mi-main.c
> > > > *** mi-main.c 17 Nov 2006 19:30:41 -0000 1.86
> > > > --- mi-main.c 30 Dec 2006 08:42:29 -0000
> > > > ***************
> > > > *** 49,54 ****
> > > > --- 49,55 ----
> > > >
> > > > #include <ctype.h>
> > > > #include <sys/time.h>
> > > > + #include <sys/resource.h>
> > >
> > > Is sys/resource.h guaranteed to be available on all supported
> > > platforms? If not, we need to add a configure-time test and enable
> > > this code only under HAVE_GETRUSAGE or some such.
> >
> > mi-main.c already uses sys/time.h. Is sys/resource.h any less widely
> > distributed?
>
> I think sys/time.h is much more wide-spread, but I might be wrong. I
> raised the issue because sys/resource.h is relatively seldom used, so
> it might be less portable.
>
> > Is there any way of finding out e.g online database?
>
> Sorry, I don't know. Anyone?
The OpenBSD getrusage(2) manpage says that the getrusage() function
call appeared in 4.2BSD. Seventh Edition Unix doesn't have it (but
doesn't have <sys/time.h> either). HP-UX 10.20 and Solaris 2.6 both
have it, so I'm pretty sure all the UNIX-like systems we support have
it. But POSIX marks it as an XSI extension, so I think we should not
rely on it.
next prev parent reply other threads:[~2006-12-31 11:58 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 8:52 Nick Roberts
2006-12-30 12:09 ` Vladimir Prus
2006-12-30 16:10 ` Eli Zaretskii
2006-12-31 3:26 ` Nick Roberts
2006-12-31 4:26 ` Eli Zaretskii
2006-12-31 6:55 ` Nick Roberts
2006-12-31 15:10 ` Daniel Jacobowitz
2007-01-01 4:11 ` Nick Roberts
2007-01-03 18:01 ` Daniel Jacobowitz
2007-01-03 21:50 ` Nick Roberts
2007-01-03 22:59 ` Daniel Jacobowitz
2007-01-04 2:50 ` Nick Roberts
2006-12-31 15:33 ` Vladimir Prus
2006-12-30 16:09 ` Eli Zaretskii
2006-12-30 22:10 ` Nick Roberts
2006-12-31 4:22 ` Eli Zaretskii
2006-12-31 4:25 ` Daniel Jacobowitz
2006-12-31 5:18 ` Nick Roberts
2006-12-31 5:49 ` Daniel Jacobowitz
2006-12-31 7:47 ` Nick Roberts
2006-12-31 15:15 ` Daniel Jacobowitz
2006-12-31 15:24 ` Mark Kettenis
2006-12-31 15:39 ` Vladimir Prus
2006-12-31 16:09 ` Mark Kettenis
2006-12-31 16:21 ` Vladimir Prus
2006-12-31 19:29 ` Daniel Jacobowitz
2006-12-31 22:08 ` Eli Zaretskii
2007-01-01 4:24 ` Nick Roberts
2007-01-01 6:06 ` Eli Zaretskii
2007-01-01 4:07 ` Nick Roberts
2007-01-01 5:58 ` Eli Zaretskii
2007-01-01 22:07 ` Nick Roberts
2007-01-02 4:20 ` Eli Zaretskii
2007-01-16 5:57 ` Nick Roberts
2007-01-16 22:17 ` Eli Zaretskii
2007-01-16 22:30 ` Nick Roberts
2007-01-16 23:01 ` Eli Zaretskii
2007-01-20 17:27 ` Eli Zaretskii
2007-01-20 20:58 ` Nick Roberts
2007-01-27 14:53 ` Eli Zaretskii
2007-01-27 15:10 ` Eli Zaretskii
2007-01-27 22:12 ` Nick Roberts
2007-01-27 22:19 ` Nick Roberts
2007-01-27 22:08 ` Nick Roberts
2007-01-28 4:17 ` Eli Zaretskii
2007-01-28 5:31 ` Nick Roberts
2007-02-02 13:33 ` Eli Zaretskii
2007-02-02 23:28 ` Nick Roberts
2007-02-03 11:10 ` Eli Zaretskii
2007-01-01 9:18 ` Nick Roberts
2007-01-01 16:21 ` Daniel Jacobowitz
2006-12-31 15:34 ` Vladimir Prus
2006-12-31 11:58 ` Mark Kettenis [this message]
2006-12-31 7:50 ` Nick Roberts
2006-12-31 18:33 ` Vladimir Prus
2007-01-01 4:18 ` Nick Roberts
2006-12-31 22:10 ` Eli Zaretskii
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=200612311158.kBVBw8x6021147@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
/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