From: Mark Kettenis <kettenis@gnu.org>
To: mark@codesourcery.com
Cc: gdb-patches@gcc.gnu.org
Subject: Re: PATCH: Introduce gdb_gettimeofday
Date: Wed, 09 Mar 2005 10:31:00 -0000 [thread overview]
Message-ID: <200503091030.j29AULdL019037@jop31.nfra.nl> (raw)
In-Reply-To: <200503082329.j28NTaN1029372@sethra.codesourcery.com> (message from Mark Mitchell on Tue, 8 Mar 2005 15:29:36 -0800)
Date: Tue, 8 Mar 2005 15:29:36 -0800
From: Mark Mitchell <mark@codesourcery.com>
Some systems (Windows) don't have gettimeofday. This patch introduces
a new utility function gdb_gettimeofday; on UNIX systems this is just
a wrapper for gettimeofday, while on other systems it relies on
fallback methods. (In particular, on Windows, we use "time", at least
for now.)
I'm not thrilled. gettimeofday(2) is POSIX, so any decent operating
system should have it. Even cygwin (the only way GDB currently
supports Windows) seems to have it. Is there a coordinated attempt to
make GDB run on Windows in some other way?
If there indeed is such an effort, did you consider adding
gettimeofday(2) to libiberty?
Tested by building on both Windows (with other patches not yet
submitted) and on x86_64-uknown-linux-gnu, and by running the
testsuite on the latter platform with no regressions. I'll check for
copyrights before submission, if this is approved.
OK?
Even if this patch turns out to be the way go, there's a problem:
2005-03-08 Mark Mitchell <mark@codesourcery.com>
* config.in (HAVE_GETTIMEOFDAY): #undef it.
This should not be necessary.
Cheers,
Mark
next prev parent reply other threads:[~2005-03-09 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 23:29 Mark Mitchell
2005-03-09 10:31 ` Mark Kettenis [this message]
2005-03-09 16:01 ` Mark Mitchell
2005-03-09 19:25 ` Stan Shebs
2005-03-09 19:28 ` Mark Mitchell
2005-03-09 22:14 ` Mark Kettenis
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=200503091030.j29AULdL019037@jop31.nfra.nl \
--to=kettenis@gnu.org \
--cc=gdb-patches@gcc.gnu.org \
--cc=mark@codesourcery.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