This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug web/61782] always_inline incorrectly documented
- From: "daniel.santos at pobox dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 14 Jul 2014 15:34:09 +0000
- Subject: [Bug web/61782] always_inline incorrectly documented
- Auto-submitted: auto-generated
- References: <bug-61782-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61782
--- Comment #2 from Daniel Santos <daniel.santos at pobox dot com> ---
Hmm, I suppose I wasn't considering that interpretation of the language. Your
clarification helps though, and actually sounds pretty good: "always_inline
forces inlining of the function under all circumstances and it is an error if
the function cannot be inlined."
I know that I am not the only person who has read the original language and
interpreted it as marking the function inline-able, even if if inlining
(-finline-functions) isn't enabled, yet still subject to other considerations
for a determination as to rather or not the function body is actually inlined,
(i.e., the inline insn count).
So can we get some clarification similar to the language you used above?