GNU bug report logs - #34527
27.0.50; Cygwin now has timer_getoverrun

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ken Brown <kbrown <at> cornell.edu>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#34527: closed (27.0.50; Cygwin now has timer_getoverrun)
Date: Fri, 22 Feb 2019 14:23:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 22 Feb 2019 14:22:27 +0000
with message-id <4c652ac2-9f5b-86bc-28eb-66f107812816 <at> cornell.edu>
and subject line Re: bug#34527: 27.0.50; Cygwin now has timer_getoverrun
has caused the debbugs.gnu.org bug report #34527,
regarding 27.0.50; Cygwin now has timer_getoverrun
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
34527: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34527
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ken Brown <kbrown <at> cornell.edu>
To: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>
Subject: 27.0.50; Cygwin now has timer_getoverrun
Date: Mon, 18 Feb 2019 15:16:32 +0000

[Message part 3 (text/plain, inline)]

The latest release of Cygwin supports the timer_getoverrun function, so
there's no longer a need for the workaround in profiler.c that defines
timer_getoverrun as a macro.  The attached patch causes the function to
be used rather than the macro when it exists.

OK for master?

Ken

[0001-Use-timer_getoverrun-on-Cygwin-when-possible.patch (text/plain, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Ken Brown <kbrown <at> cornell.edu>
Cc: "34527-done <at> debbugs.gnu.org" <34527-done <at> debbugs.gnu.org>
Subject: Re: bug#34527: 27.0.50; Cygwin now has timer_getoverrun
Date: Fri, 22 Feb 2019 14:22:27 +0000

Closing.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.