[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2017-07-19 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #29 from github-bugzi...@puremagic.com --- Commits pushed to dmd-cxx at https://github.com/dlang/druntime https://github.com/dlang/druntime/commit/8e29e0621b074a8d368b4d7d344281adb7a91e54 Add ClockType enum to core.time for issue# 13433.

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-10-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #28 from github-bugzi...@puremagic.com --- Commits pushed to stable at https://github.com/D-Programming-Language/phobos https://github.com/D-Programming-Language/phobos/commit/5f3c6f1a647c83247aea8811184d2b93f5147b46 Implement issue 13433

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-06-30 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 Jonathan M Davis changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-06-30 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #27 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/phobos https://github.com/D-Programming-Language/phobos/commit/5f3c6f1a647c83247aea8811184d2b93f5147b46 Implement issue 13433

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-06-17 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #26 from github-bugzi...@puremagic.com --- Commits pushed to stable at https://github.com/D-Programming-Language/druntime https://github.com/D-Programming-Language/druntime/commit/8e29e0621b074a8d368b4d7d344281adb7a91e54 Add ClockType enu

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-06-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 Andrei Alexandrescu changed: What|Removed |Added Version|unspecified |D2 --

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-06-06 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #25 from Jonathan M Davis --- https://github.com/D-Programming-Language/phobos/pull/2584 --

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-06-01 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #24 from Steven Schveighoffer --- (In reply to Jonathan M Davis from comment #23) > The druntime changes have been pulled, but the Phobos changes - which is > what the request is actually for - haven't been pulled yet. I have to finish >

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-06-01 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 Jonathan M Davis changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-05-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #22 from Steven Schveighoffer --- Vladimir pointed out a mechanism to make the decision at runtime. That's the only option I see here. I'm not sure how it's done, but it seems it would incur some runtime cost. But I think it could be made

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-05-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #21 from Sobirari Muhomori --- I mean, D compiler can compile 64-bit programs, which are incompatible with 32-bit systems. And I believe 64-bit linux can be set up without ability to run 32-bit executables. --

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-05-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #20 from Vladimir Panteleev --- (In reply to Sobirari Muhomori from comment #19) > Already done: 64-bit executables are incompatible with 32-bit systems. Except that: - We do not actually release separate 32-bit and 64-bit versions - 64-

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-05-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #19 from Sobirari Muhomori --- (In reply to Vladimir Panteleev from comment #18) > Makes no sense. Already done: 64-bit executables are incompatible with 32-bit systems. I think, it fits D ideology "good by default, closer to the system

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-05-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #18 from Vladimir Panteleev --- (In reply to Sobirari Muhomori from comment #17) > How about server platforms? Those are less conservative than desktop. So we release two Windows DMD builds, one for client version of Windows and one for

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-05-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #17 from Sobirari Muhomori --- (In reply to Steven Schveighoffer from comment #16) > But we can't require Windows 8 for D. How about server platforms? Those are less conservative than desktop. --

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-05-25 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 Steven Schveighoffer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-05-25 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #15 from Sobirari Muhomori --- BTW, Windows 8 has GetSystemTimePreciseAsFileTime function for time reading with better precision. --

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2015-04-29 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #14 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/druntime https://github.com/D-Programming-Language/druntime/commit/8e29e0621b074a8d368b4d7d344281adb7a91e54 Add ClockType enu

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-06 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #13 from Steven Schveighoffer --- (In reply to Jonathan M Davis from comment #12) > As I said, I'm not against adding it. It just seems to me that in most cases > where you'd be getting the time that quickly, it wouldn't make sense to onl

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-05 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #12 from Jonathan M Davis --- As I said, I'm not against adding it. It just seems to me that in most cases where you'd be getting the time that quickly, it wouldn't make sense to only have a resolution of 1 ms. And even if it's being filt

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-05 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #11 from Kevin L --- std.logger's current design doesn't permit Logger subclasses to avoid the call to Clock.currTime() before they get control of the output at Logger.beginLogMsg()/writeMsgPart()/finishLogMsg()/writeLogMsg(). It also do

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #10 from Marco Leise --- You might be right. --

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #9 from Jonathan M Davis --- https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_MRG/2/html/Realtime_Reference_Guide/sect-Realtime_Tuning_Guide-Timestamping-POSIX_Clocks.html#Realtime_Reference_Guide-Timestamping-COARSE_Clock

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #8 from Marco Leise --- I just ran a test: void main(string[] args) { while (true) { timespec time; clock_gettime(CLOCK_REALTIME_COARSE, &time); printf(":%03ld ms\n", time.tv_nsec / 1_000_000); } } My

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #7 from Marco Leise --- Do you have a source Jonathan? All I could find about it was references to the kernel ticks on Linux which is 100, 250 or 1000 Hz, but never as low as 10 Hz. On tickless systems I couldn't figure out how exactly th

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #6 from Jonathan M Davis --- https://github.com/D-Programming-Language/phobos/pull/2584 --

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-03 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #5 from Jonathan M Davis --- H. The precision of the _COARSE variants is abysmal. Apparently, it's only 1 ms (at least on Linux). So, I certainly think that it would be foolish to use them normally, but I see no problem with adding a

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-01 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 Marco Leise changed: What|Removed |Added CC||marco.le...@gmx.de --- Comment #4 from Marco L

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-10-01 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 Steven Schveighoffer changed: What|Removed |Added CC||jmdavisp...@gmx.com,

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-09-06 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 --- Comment #2 from Vladimir Panteleev --- Oh, I see - std.logger needs the realtime clock to log the time together with the log message. --

[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

2014-09-06 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=13433 Vladimir Panteleev changed: What|Removed |Added CC||thecybersha...@gmail.com --- Comment #1