Inline is used very specifically where the code has to be fast. Best is only to inline tiny parts of code that will be "inlined".
That's to say "injected" into the source code where it is needed. Otherwise it is a full jump to a distant function, with context saving. Hence the "inlining" only serves a very specific purpose. Regards. ----- Mail d'origine ----- De: rempas via Tinycc-devel <[email protected]> À: Tinycc Devel <[email protected]> Cc: [email protected] Envoyé: Mon, 06 Dec 2021 09:35:19 +0100 (CET) Objet: [Tinycc-devel] How exactly inline works and should I inline all the time? Hi! I don't know if we must only post questions that are specific to the TCC compiler specifically (even tho this question can differ from compiler to compiler) or we can make questions about C in general and in the case that the first is true then please inform me so I know. Anyway I wanted to ask how inline works specifically and not generally. I know generally that it "puts the source code" inline so we don't have to use "jmp" but is there anything else to it that I should know? Are there any dangers or reasons than someone should not use it? Also is there a way to tell the compiler to inline every function rather than always having to add the "inline" keyword? _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
