NetBSD Problem Report #2512

From gnats  Tue Jun  4 04:28:11 1996
Received: from by (8.7.4/8.6.12) with ESMTP id EAA18175 for <>; Tue, 4 Jun 1996 04:22:59 -0400 (EDT)
Message-Id: <>
Date: Tue, 4 Jun 1996 08:18:23 +0200 (MET DST)
From: Ignatios Souvatzis <>
Subject: fuword() definition problem
X-Send-Pr-Version: 3.95

>Number:         2512
>Category:       kern
>Synopsis:       fuword() definition problem
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    thorpej
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 04 04:35:01 +0000 1996
>Closed-Date:    Thu Jun 20 07:32:34 +0000 2019
>Last-Modified:  Thu Jun 20 07:32:34 +0000 2019
>Originator:     Unprivileged user
>Release:        1.1B
	M68060 support integrators, desperated

System: NetBSD 1.1B NetBSD 1.1B (DRACO) #95: Fri May 31 13:21:53 MET DST 1996 amiga

	The kernel fuword() returns a "word of data" inside an int,
	but is also supposed to return -1 on error, which is .. rather
	difficult if sizeof(int) == sizeof(word of data).

	(We dont have this problem with fusword and fubytes, because (to
	my knowledge) none of our ports uses shorts or bytes as ints).
	Furthermore, the fetch family doesn't support 64bit machines well...

	Look for more effective ways to integrate Motorola's m68060 software
	support package than calling copyin()/copyout() for the transfer of
	bytes, int16s and int32s. Find fuxxx() and suxxx(). Read prototypes.
	Read implementation. Scratch head. Sigh.
	First problem: not known, with the exception of possibly taking a 
	pointer to a place to store it to as an argument.
	On m68k, this can still be implemented in a more effective
	way than just calling copyin.

	2nd problem: I can imagine that fuint8, fuint16, fuint32
	and fuint64 would be needed, with fuword and fusword mapped
	on a per-arch-basis to one of them.

Responsible-Changed-From-To: kern-bug-people->thorpej
Responsible-Changed-When: Mon, 27 May 2019 12:39:15 +0000
Over to thorpej who recently removed fuword for another API. Does the new API handle all the points raised here?

State-Changed-From-To: open->closed
State-Changed-When: Thu, 20 Jun 2019 07:32:34 +0000
This has been addressed by the ufetch(9) and ustore(9) APIs.


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD:,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.