[Issue 18989] On OSX32, core.stdc.time.clock() should resolve to clock$UNIX2003()

2018-06-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18989 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/druntime https://github.com/dlang/druntime/commit/4c9c74adf45481ef0f87360ae6b60a2b3a03b740 fix Issue 18989 - On OSX32, core.stdc.time.clock()

[Issue 18989] On OSX32, core.stdc.time.clock() should resolve to clock$UNIX2003()

2018-06-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18989 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 18989] On OSX32, core.stdc.time.clock() should resolve to clock$UNIX2003()

2018-06-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18989 --- Comment #2 from Walter Bright --- https://github.com/dlang/druntime/pull/2216 --

[Issue 18989] On OSX32, core.stdc.time.clock() should resolve to clock$UNIX2003()

2018-06-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18989 --- Comment #1 from Walter Bright --- It's defined in the system headers as: clock_t clock(void) __asm("_" "clock" "$UNIX2003"); --