From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Support for ITIMER_PROF?
Date: Mon, 22 Jun 2015 21:07:00 -0000 [thread overview]
Message-ID: <558878FD.3050909@cornell.edu> (raw)
In-Reply-To: <20150622132541.GA21402@calimero.vinschen.de>
On 6/22/2015 9:25 AM, Corinna Vinschen wrote:
> On Jun 22 08:05, Ken Brown wrote:
>> According to the Cygwin API documentation
>> (https://cygwin.com/cygwin-api/std-notes.html), "getitimer and setitimer
>> only support ITIMER_REAL for now." I'm wondering whether there's any chance
>> that support for ITIMER_PROF might be added. I have no idea what the
>> obstacles are.
>>
>> My reason for asking is that emacs has a CPU profiling function, which
>> doesn't work on Cygwin because it relies on ITIMER_PROF. (There's an
>> alternative implementation, but it requires timer_getoverrun, also not
>> available in Cygwin.)
>
> Both very tricky. Given the description of timer_getoverrun and how
> this stuff is implemented in Cygwin, you might get away with
>
> #ifdef __CYGWIN__
> #define timer_getoverrun(x) 0
> #endif
>
> indepedently of using SIGEV_SIGNAL or SIGEV_THREAD.
This seems to work. Thanks!
One question: It seems that SIGEV_SIGNAL and friends are defined as macros on
Linux (or at least on the one Linux distribution I looked at), but on Cygwin
they're only enum constants. And emacs expects them to be defined as macros.
Would something like the following be reasonable for the sake of compatibility?
--- a/winsup/cygwin/include/cygwin/signal.h
+++ b/winsup/cygwin/include/cygwin/signal.h
@@ -311,6 +311,10 @@ enum
perform notification */
};
+#define SIGEV_SIGNAL SIGEV_SIGNAL
+#define SIGEV_NONE SIGEV_NONE
+#define SIGEV_THREAD SIGEV_THREAD
+
#if __WORDSIZE == 64
typedef __uint64_t sigset_t;
#else
Ken
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-06-22 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 12:05 Ken Brown
2015-06-22 13:25 ` Corinna Vinschen
2015-06-22 21:07 ` Ken Brown [this message]
2015-06-23 8:43 ` Corinna Vinschen
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=558878FD.3050909@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.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).