mirror of
https://github.com/MidnightCommander/mc
synced 2024-12-22 20:36:50 +03:00
e064bd60df
...or not-so-large but nevertheless contain more than one function call, or contain loops, or contain if's and at least one function call, or contain largish objects on stack. In my experience, in those cases the code size growth is big enough to not inline stuff. I guess some of the really big functions are defined inline because they have, or had in the past, just one callsite. But for a few years gcc already does it automatically, no need to do it by hand and risk code size explosion when later during code evolution another callsite is created. This optimization by hand is simply no longer needed. Anyway, here is the code size difference: text data bss dec hex filename 572337 17944 177820 768101 bb865 mc.t5/.obj/src/mc 567697 17944 177820 763461 ba645 mc.t6/.obj/src/mc Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com> Signed-off-by: Sergei Trofimovich <slyfox@inbox.ru> |
||
---|---|---|
.. | ||
.gitignore | ||
bookmark.c | ||
choosesyntax.c | ||
edit-impl.h | ||
edit-widget.h | ||
edit.c | ||
edit.h | ||
editcmd_dialogs.c | ||
editcmd_dialogs.h | ||
editcmd.c | ||
editcmddef.h | ||
editdraw.c | ||
editkeys.c | ||
editlock.c | ||
editlock.h | ||
editmenu.c | ||
editoptions.c | ||
editwidget.c | ||
etags.c | ||
etags.h | ||
Makefile.am | ||
syntax.c | ||
usermap.c | ||
usermap.h | ||
wordproc.c |