ESECT macro question
by Ilias Stamatis
Hi everyone,
As I'm going through the code I noticed that some functions have the ESECT
macro in their signature. Here's how ESECT is defined:
/** Put infrequently used env functions in separate section */
# ifdef __APPLE__
# define ESECT __attribute__ ((section("__TEXT,text_env")))
# else
# define ESECT __attribute__ ((section("text_env")))
# endif
So, to my understanding those pieces of code / functions are put in a
separate binary section other than the standard "text" section that they
would end up normally. The comment says that this applies to infrequently
used functions.
I suspect this has something to do with caching but I'm not sure how it
helps exactly. Could someone please clarify this?
Thanks!
5 years, 8 months