From owner-freebsd-standards@FreeBSD.ORG  Mon Mar  8 23:47:37 2010
Return-Path: <owner-freebsd-standards@FreeBSD.ORG>
Delivered-To: freebsd-standards@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 179631065670;
	Mon,  8 Mar 2010 23:47:37 +0000 (UTC)
	(envelope-from jilles@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id E29298FC1D;
	Mon,  8 Mar 2010 23:47:36 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o28Nlach031440;
	Mon, 8 Mar 2010 23:47:36 GMT
	(envelope-from jilles@freefall.freebsd.org)
Received: (from jilles@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o28NlasK031436;
	Mon, 8 Mar 2010 23:47:36 GMT (envelope-from jilles)
Date: Mon, 8 Mar 2010 23:47:36 GMT
Message-Id: <201003082347.o28NlasK031436@freefall.freebsd.org>
To: emz@norma.perm.ru, jilles@FreeBSD.org, freebsd-standards@FreeBSD.org
From: jilles@FreeBSD.org
Cc: 
Subject: Re: standards/144448: [libm] sin(3) broken in libm on amd64
X-BeenThere: freebsd-standards@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Standards compliance <freebsd-standards.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-standards>, 
	<mailto:freebsd-standards-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-standards>
List-Post: <mailto:freebsd-standards@freebsd.org>
List-Help: <mailto:freebsd-standards-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-standards>, 
	<mailto:freebsd-standards-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 23:47:37 -0000

Synopsis: [libm] sin(3) broken in libm on amd64

State-Changed-From-To: open->closed
State-Changed-By: jilles
State-Changed-When: Mon Mar 8 23:47:35 UTC 2010
State-Changed-Why: 
Submitter confirms this is not a bug in FreeBSD.

http://www.freebsd.org/cgi/query-pr.cgi?pr=144448