From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by yquem.inria.fr (Postfix) with ESMTP id 6003ABB9C for ; Wed, 16 Nov 2005 19:55:44 +0100 (CET) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id jAGIthRU004742 for ; Wed, 16 Nov 2005 19:55:43 +0100 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id TAA28896; Wed, 16 Nov 2005 19:55:43 +0100 (MET) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id jAGItex3004733; Wed, 16 Nov 2005 19:55:42 +0100 Received: from rosella (ppp7-104.lns1.syd7.internode.on.net [59.167.7.104]) by smtp1.adl2.internode.on.net (8.12.9/8.12.6) with ESMTP id jAGItBas021790; Thu, 17 Nov 2005 05:25:16 +1030 (CST) (envelope-from skaller@users.sourceforge.net) Subject: Re: [Caml-list] THREADED_CODE: Why CODE32 defined on x86-64? From: skaller To: Xavier Leroy Cc: Richard Jones , caml-bugs@pauillac.inria.fr, caml-list@inria.fr In-Reply-To: <437B4E73.5020503@inria.fr> References: <20051116152330.GA9895@furbychan.cocan.org> <437B4E73.5020503@inria.fr> Content-Type: text/plain Date: Thu, 17 Nov 2005 05:55:10 +1100 Message-Id: <1132167310.31678.161.camel@rosella> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Miltered: at concorde with ID 437B80AF.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at concorde with ID 437B80AC.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 loader:01 model:01 statically:01 opcode:01 wrote:01 sourceforge:01 dynamically:01 defined:01 constraints:02 constraints:02 dynamic:03 threaded:03 static:03 shared:04 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.3 On Wed, 2005-11-16 at 16:21 +0100, Xavier Leroy wrote: > I would have expected the dynamic loader to implement the small model > like the static linker does, but from what you say it's not the case. The modelling constraints only apply to a statically linked image. The reason is that the constraints allow offsets for various instructions to 'fit' in the opcode. Dynamically loaded *shared* libraries are accessed indirectly via tables .. so it doesn't matter where they're loaded. -- John Skaller Felix, successor to C++: http://felix.sf.net