From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id A46733858C5F; Tue, 21 Mar 2023 20:03:08 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A46733858C5F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1679428988;
	bh=JigjwaoVjCQbvXRIyU1mJVa1GrWSx4YSTcGRx3lzHtk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=LIMyfY8KBSe7+JvY4Ieg6CyBXeJhtVQm5rkDkFNuX89jACjazJ1OwXRPwV6E6gaL7
	 Pmp5oEvz7Kx/Ra521ujM+5AtQWNFtu8pjbw5k3d3p5QjlQN5lU9Yj7/DofNnjmgy28
	 cfLY1TdpPD1847AsHTWBNcXUCpkWUY0/47HPwX4M=
From: "adhemerval.zanella at linaro dot org"
 <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug time/30200] time sometimes appears to go backwards
Date: Tue, 21 Mar 2023 20:03:08 +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: adhemerval.zanella at linaro dot org
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: 
Message-ID: <bug-30200-131-RkBSTK7gye@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30200-131@http.sourceware.org/bugzilla/>
References: <bug-30200-131@http.sourceware.org/bugzilla/>
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: <glibc-bugs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30200

--- Comment #16 from Adhemerval Zanella <adhemerval.zanella at linaro dot o=
rg> ---
(In reply to Bruno Haible from comment #15)
> (In reply to Adhemerval Zanella from comment #14)
> > Florian explicit say he would revert it
> > on RH distros because of performance implications.=20
>=20
> If the question cannot be decided due to different distro priorities (for
> some distros, logging speed is super important, while for other distros,
> correctness and interoperability is the focus), then how about changing t=
he
> patch so that it adds a glibc configure option? Such as
> --enable/disable-fast-time or --enable/disable-correct-time?

A configure switch for this specific issue is the last thing I would like to
do, it adds another build permutation and will only move the issue to
distribution maintainers.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=