From owner-freebsd-current  Sat Jan 11 21: 4:25 2003
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8178037B401; Sat, 11 Jan 2003 21:04:24 -0800 (PST)
Received: from soulshock.mail.pas.earthlink.net (soulshock.mail.pas.earthlink.net [207.217.120.130])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B004443F3F; Sat, 11 Jan 2003 21:04:23 -0800 (PST)
	(envelope-from tlambert2@mindspring.com)
Received: from stork (stork.mail.pas.earthlink.net [207.217.120.188])
	by soulshock.mail.pas.earthlink.net (8.11.6+Sun/8.11.6) with ESMTP id h0C4gmH11327;
	Sat, 11 Jan 2003 20:42:48 -0800 (PST)
Received: from pool0059.cvx22-bradley.dialup.earthlink.net ([209.179.198.59] helo=mindspring.com)
	by stork with asmtp (SSLv3:RC4-MD5:128)
	(Exim 3.33 #1)
	id 18XZx0-0000J4-00; Sat, 11 Jan 2003 20:42:23 -0800
Message-ID: <3E20F1CC.DD77F760@mindspring.com>
Date: Sat, 11 Jan 2003 20:40:44 -0800
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Kris Kennaway <kris@obsecurity.org>
Cc: sparc@FreeBSD.org, current@FreeBSD.org
Subject: Re: fpsetmask on sparc64
References: <20030112031626.GA15783@rot13.obsecurity.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40873e2a9908a277f03e4b22bcbf388f3350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Kris Kennaway wrote:
> fpsetmask is not defined in <floatingpoint.h> or
> <machine/floatingpoint.h> on sparc64 (it is on i386):
[ ... ]
> Is this an omission, or are the ports wrong?

An OS abstracts the differences in underlying hardware, for the
benefit of the software it hosts.  If there is code that compiles
on FreeBSD for one platform, and does not compile on FreeBSD for
another, either the code is hardware-specific, or the OS is not
doing its job.

In this case, I believe the OS is not doing its job, according to
POSIX.

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message