http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56919
Janne Blomqvist <jb at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2013-05-15
Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org
Summary|[4.7/4.8/4.9 Regression] |[4.7/4.8 Regression] Wrong
|Wrong result for |result for SYSTEM_CLOCK on
|SYSTEM_CLOCK on Cygwin |Cygwin
Ever confirmed|0 |1
--- Comment #7 from Janne Blomqvist <jb at gcc dot gnu.org> ---
Issue is fixed on trunk (4.9).
The question is whether it's useful to backport to 4.7 and 4.8. The previous
cygwin behavior, while perhaps surprising, isn't wrong per se and while the new
behavior is an improvement (IMHO) it's a (subtle) change in behavior which
might be surprising in the middle of a release series.
Maybe just backport the _POSIX_MONOTONIC_CLOCK part to fix(?) newlib targets,
and leave the windows stuff as is?
