Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

12
  • 3
    You can look at the output of the compiler: godbolt.org/z/XZ_0NN (Spoiler: endless loop) Commented Apr 8, 2019 at 14:26
  • 1
    Perhaps I'm not understanding the question, but didn't you just find out how gcc behaves in this situation? Commented Apr 8, 2019 at 14:27
  • Do you see the same behavior if you use the standard keyword, inline, instead of the implementation extension, __inline__? Commented Apr 8, 2019 at 14:27
  • @mch Thank you for the resource, I had never come across that tool! Commented Apr 8, 2019 at 14:29
  • 1
    No, @SaucyGoat, __inline__ has never been a keyword of any version of standard C, and it is unlikely to be a keyword of any future version, as its form is reserved for implementation use. Do not confuse implementation extensions (such as __inline__) with standard features, and do not confuse studying the behavior of a specific implementation with studying the behavior required of all conforming implementations. Commented Apr 8, 2019 at 14:37