You can declare a noinline inline function.<\/p>\n
void g();\r\n\r\n\/\/ gcc\r\n__attribute__((noinline)) inline void f()\r\n{\r\n g();\r\n}\r\n\r\n\/\/ MSVC\r\n__declspec(noinline) inline void f()\r\n{\r\n g();\r\n}\r\n\r\nvoid tryme()\r\n{\r\n f();\r\n f();\r\n}\r\n<\/pre>\nWhat sorcery is this, a function that is both inline and not-inline?<\/p>\n
The two keywords are not contradictory because they describe different senses of the word “inline”.<\/p>\n
The C++ language keyword inline<\/code> means “can be defined in multiple translation units without triggering an ODR violation.” In other words, it lets you put the function definition in a header file that is included by multiple C++ files.<\/p>\nThe function attribute\/declaration specifier noinline<\/code> means “do not inline this function during code generation.” It is a directive to the optimizer not to perform inline substitution during code generation.<\/p>\nHistorically, the inline<\/code> C++ keyword was originally an optimizer hint, but optimizers were given permission to ignore it and make their own decisions about inline substitution during code generation. Nowadays, compilers pretty much ignore the optimization aspect of the inline<\/code> keyword. The only thing that remains of the inline<\/code> keyword is the ability to have multiple definitions without violating ODR.<\/p>\nYou could say that the modern sense of the C++ keyword inline<\/code> is “defined right here.” It’s a statement about the source code, not the object code.<\/p>\nIn the above example, the function f<\/code> is a noinline inline function. The inline<\/code> keyword allows the definition of f<\/code> to go into a header file that is consumed by multiple translation units. The noinline attribute\/declaration specifier tells the optimizer to emit code for f<\/code> and call it, rather than embedding the body of f<\/code> into its call sites. The function tryme<\/code> will call the function f<\/code> twice, instead of optimizing out the call and just calling g<\/code> twice.<\/p>\n","protected":false},"excerpt":{"rendered":"Two different senses of the word inline.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[25],"class_list":["post-103777","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"
Two different senses of the word inline.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/103777","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=103777"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/103777\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=103777"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=103777"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=103777"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}