Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!usc!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpcc01!hpcuhb!hpcllla!hpclisp!cary@hpclcac.HP.COM
From: cary@hpclcac.HP.COM (Cary Coutant)
Newsgroups: comp.sys.hp
Subject: Re: The Real Scoop with Shared/Demand Load  -- HELP !!!
Message-ID: <1340134@hpclcac.HP.COM>
Date: 25 Jul 90 17:38:02 GMT
References: <543@dptechno.UUCP>
Organization: Hewlett-Packard Calif. Language Lab
Lines: 31

A demand-loadable file is always sharable also.  Thus, there are
only three valid combinations:

	non-sharable, non-demand-loadable (-N)
	sharable, non-demand-loadable (-n)
	sharable, demand-loadable (-q)

Specifying both -n and -q is merely redundant, since you would be
asking for sharable and demand-loadable, so -q alone would be
equivalent.  Specifying -N and -q would be a conflict, and I'm
not sure which one would have precedence on the s300 (on the s800,
-N overrides -q).

On the s300, in the absence of any -n/-N or -q/-Q options,
the linker will automatically decide between non-demand-loadable
and demand-loadable, based on the size of the text.  Thus, it
might make sense to specify -Q if you wanted to force a program
to be non-demand-loadable.

On the s800, the default is always sharable, non-demand-loadable.
Non-sharable programs are not supported on the 800, so the -N
option is useful only for preparing things like kernels, boot images,
and dynamic load images (in conjunction with ld -A).

I believe the sticky bit is effective for sharable programs of
both flavors.


Cary Coutant
HP California Language Lab
Series 800 Linker Project