Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!panda!teddy!jpn
From: jpn@teddy.UUCP (John P. Nelson)
Newsgroups: comp.unix.wizards,comp.lang.c,comp.unix.questions
Subject: Re: New feature of Ultrix C compilers
Message-ID: <4380@teddy.UUCP>
Date: Mon, 28-Sep-87 13:02:53 EDT
Article-I.D.: teddy.4380
Posted: Mon Sep 28 13:02:53 1987
Date-Received: Tue, 29-Sep-87 06:01:07 EDT
References: <867@sask.UUCP>
Reply-To: jpn@teddy.UUCP (John P. Nelson)
Organization: GenRad, Inc., Concord, Mass.
Lines: 15
Keywords: VAX C
Xref: mnetor comp.unix.wizards:4553 comp.lang.c:4593 comp.unix.questions:4300

>We just installed Ultrix 2.0 on a uVax-II. Last night I 
>recompiled a couple of C programs using both the VAX C 
>compiler and the default comnpiler. The new executables were 
>~2.5 times the size of the old one. 

This has nothing to do with the Compiler per-se:  It is related to the
C library.  Ultrix 2.0 supports NFS and YP (yellow pages).  No doubt
your (relatively small) program calls pwuid() (or other password file
routines).  Since the password file can now be shared via yellow pages,
the entire yellow pages library is loaded.

Of course, if you do not use YP, you still have to carry around the YP
code.  I don't know of any way to prevent this.  Note that since ULTRIX
defaults to demand-page loading of tasks, if you do not use YP, this
code never even get loaded off disk!