rename __simple_malloc.c to lite_malloc.c - yes this affects behavior!

why does this affect behavior? well, the linker seems to traverse
archive files starting from its current position when resolving
symbols. since calloc.c comes alphabetically (and thus in sequence in
the archive file) between __simple_malloc.c and malloc.c, attempts to
resolve the "malloc" symbol for use by calloc.c were pulling in the
full malloc.c implementation rather than the __simple_malloc.c
implementation.

as of now, lite_malloc.c and malloc.c are adjacent in the archive and
in the correct order, so malloc.c should never be used to resolve
"malloc" unless it's already needed to resolve another symbol ("free"
or "realloc").

1 files changed, 0 insertions, 0 deletions

diff --git a/src/malloc/__simple_malloc.c b/src/malloc/lite_malloc.c
index c8293908..c8293908 100644
--- a/src/malloc/__simple_malloc.c
+++ b/src/malloc/lite_malloc.c