You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While browsing the code base I found two macros: ALLINONE and EXPORT. Is there any value this functionality brings to the software? Because I could not figure out why it is beneficial to have just a single translation unit. In a brief correspondence with the current owner of the project, @Rudde, s/he said s/he did not know the origins of these two macros. So this question is mainly directed towards the original author, @esmil (as far as I know).
The text was updated successfully, but these errors were encountered:
As far as I recall this was like a poor mans LTO way before it existed in GCC. Similar to LTO compiling everything as a single translation unit allows the compiler to do optimizations (inlining, constant propagation etc.) across files. It was probably never worth it, but these days you can just add -flto to CFLAGS to get a similar effect.
While browsing the code base I found two macros: ALLINONE and EXPORT. Is there any value this functionality brings to the software? Because I could not figure out why it is beneficial to have just a single translation unit. In a brief correspondence with the current owner of the project, @Rudde, s/he said s/he did not know the origins of these two macros. So this question is mainly directed towards the original author, @esmil (as far as I know).
The text was updated successfully, but these errors were encountered: