From: skaller <skaller@users.sourceforge.net>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: Richard Jones <rich@annexia.org>,
caml-bugs@pauillac.inria.fr, caml-list@inria.fr
Subject: Re: [Caml-list] THREADED_CODE: Why CODE32 defined on x86-64?
Date: Thu, 17 Nov 2005 05:55:10 +1100 [thread overview]
Message-ID: <1132167310.31678.161.camel@rosella> (raw)
In-Reply-To: <437B4E73.5020503@inria.fr>
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 <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
prev parent reply other threads:[~2005-11-16 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 15:23 Richard Jones
2005-11-16 15:21 ` [Caml-list] " Xavier Leroy
2005-11-16 16:36 ` Richard Jones
2005-11-16 18:55 ` skaller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1132167310.31678.161.camel@rosella \
--to=skaller@users.sourceforge.net \
--cc=Xavier.Leroy@inria.fr \
--cc=caml-bugs@pauillac.inria.fr \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).