08a4cc0969
By force-inlining everything that would otherwise be a macro, we get the same effect (it's not clear in the first place that this is actually a good idea, but it avoids making any changes to the existing performance profile). This makes the code more maintainable (in anticipation of subsequent changes), as well as making performance profiles and debug info more readable (we get "real" line numbers, instead of making everything point to the macro definition of all associated functions).
7 lines
232 B
C
7 lines
232 B
C
#include "jemalloc/internal/jemalloc_preamble.h"
|
|
#include "jemalloc/internal/jemalloc_internal_includes.h"
|
|
|
|
ph_gen(, edata_avail, edata_t, avail_link,
|
|
edata_esnead_comp)
|
|
ph_gen(, edata_heap, edata_t, heap_link, edata_snad_comp)
|