From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30187 invoked by alias); 15 May 2013 15:28:37 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 30138 invoked by uid 48); 15 May 2013 15:28:34 -0000 From: "jb at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/56919] [4.7/4.8 Regression] Wrong result for SYSTEM_CLOCK on Cygwin Date: Wed, 15 May 2013 15:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jb at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: jb at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.7.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to short_desc everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-05/txt/msg01042.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56919 Janne Blomqvist 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 --- 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?