From owner-cvs-all@FreeBSD.ORG Fri Mar 19 19:54:30 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7135916A4CE; Fri, 19 Mar 2004 19:54:30 -0800 (PST) Received: from mail018.syd.optusnet.com.au (mail018.syd.optusnet.com.au [211.29.132.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AE6643D1D; Fri, 19 Mar 2004 19:54:26 -0800 (PST) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) i2K3sM514029; Sat, 20 Mar 2004 14:54:23 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i2K3sMSU033699; Sat, 20 Mar 2004 14:54:22 +1100 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost)i2K3sMmD033698; Sat, 20 Mar 2004 14:54:22 +1100 (EST) (envelope-from jeremyp) Date: Sat, 20 Mar 2004 14:54:22 +1100 From: Peter Jeremy To: Maho Nakata Message-ID: <20040320035421.GS56509@cirb503493.alcatel.com.au> References: <200403190420.i2J4KCAH015119@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403190420.i2J4KCAH015119@repoman.freebsd.org> User-Agent: Mutt/1.4.2i cc: cvs-ports@freebsd.org cc: cvs-all@freebsd.org cc: ports-committers@freebsd.org Subject: Re: cvs commit: ports/biology/pymol Makefile ports/math/atlas Makefile ports/math/atlas-devel Makefile X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Mar 2004 03:54:30 -0000 On Thu, Mar 18, 2004 at 08:20:12PM -0800, Maho Nakata wrote: > Here is the comment form obrien: > "-fpic" is a [minor?] optimization for machines that can handle it: The "-fpic" limits are defined by the size of the displacement available in the "register+displacement" memory reference format. If the GOT entry offset won't fit into the displacement field then you need an extra 1 or 2 instructions (depending on the architecture) and a work register for every GOT access. In many (most?) cases, the GOT reference is a load and the load target register can be used as the work register. This bloats both size and runtime - though the exact impact is application dependent. You can readily measure the impact on "small" applications by compiling them with both "-fpic" and "-fPIC" on one of the affected architectures and comparing. Peter