|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#34527: closed (27.0.50; Cygwin now has timer_getoverrun) |
Date: | Fri, 22 Feb 2019 14:23:01 +0000 |
Your message dated Fri, 22 Feb 2019 14:22:27 +0000 with message-id <address@hidden> 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 address@hidden) -- 34527: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34527 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: 27.0.50; Cygwin now has timer_getoverrun Date: Mon, 18 Feb 2019 15:16:32 +0000 User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 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? Ken0001-Use-timer_getoverrun-on-Cygwin-when-possible.patch
Description: 0001-Use-timer_getoverrun-on-Cygwin-when-possible.patch
--- End Message ---
--- Begin Message ---Subject: Re: bug#34527: 27.0.50; Cygwin now has timer_getoverrun Date: Fri, 22 Feb 2019 14:22:27 +0000 User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 Closing.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |