Have I missed anything? The documentation for TCC 0.27 states that the inline keyword is ignored....
Antonio <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Libre de virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> Missatge de Antonio Prates <antoniopra...@gmail.com> del dia dt., 7 de des. 2021 a les 0:35: > Also note you can't inline recursive functions, and other restrictions > could apply. > > Maybe have a look into this thread on quora: > https://www.quora.com/Can-a-inline-function-be-recursive > > On Dec 6 2021, at 6:23 pm, david.k...@libertysurf.fr wrote: > > > 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 <tinycc-devel@nongnu.org> > > À: Tinycc Devel <tinycc-devel@nongnu.org> > > Cc: rem...@tutanota.com > > 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 > > Tinycc-devel@nongnu.org > > https://lists.nongnu.org/mailman/listinfo/tinycc-devel > > > > > > _______________________________________________ > > Tinycc-devel mailing list > > Tinycc-devel@nongnu.org > > https://lists.nongnu.org/mailman/listinfo/tinycc-devel > > > > _______________________________________________ > Tinycc-devel mailing list > Tinycc-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/tinycc-devel >
_______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
