HP3000-L Archives

March 1995, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steve Elmer <[log in to unmask]>
Reply To:
Steve Elmer <[log in to unmask]>
Date:
Tue, 28 Mar 1995 17:48:08 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Scott Herman ([log in to unmask]) wrote:
: At 10:45 PM 3/23/95 GMT, Mike Paivinen wrote:
: >Bruce Toback ([log in to unmask]) wrote:
: >: The inclusion of all the library code is what makes the POSIX program
: >: three times larger than the non-POSIX program.
: >
: >Just to pick a nit, all of the POSIX C library code is *not* in /lib/libc.a.
: >Each routine in /lib/libc.a is an interface routine between the program and
: >the real POSIX library code in XL.PUB.SYS.  We had to do this because
: >shared globals had not been implemented at the time POSIX was first released
: >on MPE/iX 4.5.
: >
 
: but shared globals are now available in 5.0, right?
: So why continue burdening us, and our executables, with the additional
overhead?
 
Yes, shared globals is in 5.0.  Also, redundant routines from /lib/libc.a and
XL.PUB.SYS have been removed from /lib/libc.a (such as a lot of the ANSI
routines that do not differ between POSIX and pre-POSIX C).  It would be
interesting to see what routines from /lib/libc.a were actually linked into
the program.  I seem to remember a bug where the whole library would be
linked in instead of just the routines referenced by the program.  If this
is the case, then that would explain the overlarge size of the program.
 
The POSIX library routines are very small, typically only calling the XL
and setting errno before returning to the caller.  This would not account
for such an increase in your program size (IMHO).
 
Steve

ATOM RSS1 RSS2