From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8D5253858C66; Mon, 6 Mar 2023 12:25:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8D5253858C66 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1678105522; bh=o8/g8z6HREdjvoe//EaDp3n8xDTHzKwR3SBFjovle2g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=I6cY26FhLrwNK7WrWzzhPNaHCCI18ud7v0W2Q/za+ybTGMkj2HlzE5zB5KiGGSEAj 9HfbJ3aop1gvJ72D88pnlIZXOfQW5rhWezUKE+qFTye9fsn21g2JAyRkdPdsUe3G3O 9lejibQaEEKY8Bs02XajZAxkM8/ppO1N4u6YgYeA= From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug time/30200] time sometimes appears to go backwards Date: Mon, 06 Mar 2023 12:25:22 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: time X-Bugzilla-Version: 2.35 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30200 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com --- Comment #7 from Florian Weimer --- (In reply to Adhemerval Zanella from comment #6) > I agree that it makes sense to use the same clock for time and timespec_g= et, > however, using CLOCK_REALTIME would make the vDSO optimization for x86_64 > and powerpc64 unusable (not a big deal IMHO). And another question is > whether we will need to add a compact symbol to time (and I also do not > think it would make sense either). CLOCK_REALTIME still has vDSO acceleration in many cases on x86-64, right? = It's just a bit slower, and the difference can matter to some logging frameworks= if I recall correctly. Bruno, the standard sources you cite suggest that we should round the secon= ds since epoch, and not (mostly) truncate it. So the standards seem to permit = such divergence already (although the rounding it as suggested would move the le= ss precise timestamp forward, not backwards). --=20 You are receiving this mail because: You are on the CC list for the bug.=