From owner-freebsd-standards@FreeBSD.ORG Tue May 3 14:13:05 2005 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4828F16A4CE for ; Tue, 3 May 2005 14:13:05 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id A84AC43D8D for ; Tue, 3 May 2005 14:13:03 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-a040.otenet.gr [212.205.215.40]) j43EBJrr022621; Tue, 3 May 2005 17:11:21 +0300 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.3/8.13.3) with ESMTP id j43ECN4l001105; Tue, 3 May 2005 17:12:23 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.13.3/8.13.3/Submit) id j43ECKXV001101; Tue, 3 May 2005 17:12:20 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Tue, 3 May 2005 17:12:20 +0300 From: Giorgos Keramidas To: "M. Warner Losh" Message-ID: <20050503141220.GA925@gothmog.gr> References: <20050420155407.GA844@falcon.midgard.homeip.net> <84dead720504200910441b9108@mail.gmail.com> <20050420162332.GB52948@orion.daedalusnetworks.priv> <20050429.005317.69580336.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050429.005317.69580336.imp@bsdimp.com> cc: freebsd-standards@freebsd.org Subject: Re: Standard type for code pointers? X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2005 14:13:05 -0000 On 2005-04-29 00:53, "M. Warner Losh" wrote: > In message: <20050420162332.GB52948@orion.daedalusnetworks.priv> > Giorgos Keramidas writes: > : > Is 'register_t' guaranteed to be wide enough? > : > : AFAIK, no. Portable C code cannot assume that a function pointer is > : small enough to fit in a single machine register. Some obscure > : architecture may choose to represent function entry points with as > : many register as it needs. > > You mean like medium model (64k data, larger code) 8086 :-) Bingo! Memory models was precicely the thing I had in mind :-)