www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/04/21/15:28:53

From: "Charles W. Kann" <ckann AT seas DOT gwu DOT edu>
Subject: Re: Multiple references in a link step
To: rdc AT freenet DOT vancouver DOT bc DOT ca
Date: Fri, 21 Apr 1995 13:45:05 -0400 (EDT)
Cc: den AT aisinc DOT com, djgpp AT sun DOT soe DOT clarkson DOT edu

> 
> 
> Just Unzip the library sources ...
> compile with gcc (verbosly) and redo the link step without -l ...
> now see whats missing and include the individual 'C' (C++) source for the lib
> that is missing adding in funtions until errors are gone.
> 
> This produces tiny packages; one can rewrite the program to use sprintf()
> and fput() instead of the whole printf() works and save a few K; similar
> savings are possible in other areas.
> 
> This is an uncommon use as the compiler is quite optimal as it is.
> 
> You'd only want to do this if you had a memory hole you wanted to fill with
> a driver or wanted to embed it in limited rom - dollor for ram chip it not
> worth the extra effort in many cases.
> 
> Rob

The problem is actually for someone else who does not read the list.  He
is trying to see if he can port a p-threads package to dos (class project).  
This means that things like malloc (and alot of other stuff) has to be 
guarenteed to be atomic since he will be simulating task switches.  I have not
looked into the code for the standard libraries, but I will also suggest that
to him to see if he can get by with the standard code.  But this is why we 
are overwriting some of these routines.

I guess I should have given the background.

Chuck Kann

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019