summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorRich Felker <dalias@aerifal.cx>2011-03-30 09:29:49 -0400
committerRich Felker <dalias@aerifal.cx>2011-03-30 09:29:49 -0400
commit620a1346382f9e10b516bc168f86d499b6716769 (patch)
tree6dab9801089447ca15d25620d7d002a461079dca /src
parent02084109f0f0d6e0a7fe4a8cb3a90a422725e264 (diff)
downloadmusl-620a1346382f9e10b516bc168f86d499b6716769.tar.gz
musl-620a1346382f9e10b516bc168f86d499b6716769.tar.bz2
musl-620a1346382f9e10b516bc168f86d499b6716769.tar.xz
musl-620a1346382f9e10b516bc168f86d499b6716769.zip
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").
Diffstat (limited to 'src')
-rw-r--r--src/malloc/lite_malloc.c (renamed from src/malloc/__simple_malloc.c)0
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