delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1997/11/09/13:12:43

From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9711091811.AA11422@clio.rice.edu>
Subject: Re: malloc()
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Sun, 9 Nov 1997 12:11:15 -0600 (CST)
Cc: sjmachin AT lexicon DOT net DOT au, djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.971109132539.11584Q-100000@is> from "Eli Zaretskii" at Nov 9, 97 01:26:05 pm

> > (2) I'm not wildly excited about the idea of FTPing emacs source, 
> 
> Tough.  I don't see how could you test this with any real-world
> program without downloading some sources.

While this is true, I don't think emacs is represetative of all programs
out there - it's just a huge application - and no more important than 
any other program out there.  Using emacs as the test bed ends up with
a malloc package optimized for - emacs.  Someone wanting to improve the
libc shouldn't be forced to test a single monster application he is not
interested in.

If a monster app is to be tested, I think it should be a recompile of GCC
with itself using the new package - and some of the pathalogical data
initialization codes to see how they perform in both memory and speed.

In any case, the person who does the testing must ultimately convince
DJ the code is stable, meets the copyright requirements, and has been
adequately tested.  

- Raw text -


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