|author||Rich Felker <email@example.com>||2011-03-30 09:29:49 -0400|
|committer||Rich Felker <firstname.lastname@example.org>||2011-03-30 09:29:49 -0400|
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").
|-rw-r--r--||src/malloc/lite_malloc.c (renamed from src/malloc/__simple_malloc.c)||0|
1 files changed, 0 insertions, 0 deletions