public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/61782] always_inline incorrectly documented
Date: Tue, 15 Jul 2014 09:12:00 -0000	[thread overview]
Message-ID: <bug-61782-4-IhT42Tc2Fr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61782-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61782

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Like

@item always_inline
@cindex @code{always_inline} function attribute
Generally, functions are not inlined unless optimization is specified.
For functions declared inline, this attribute inlines the function 
independent of any restrictions that otherwise apply to inlining.
Failure to inline such function is diagnosed as error.
Note that if such function is called indirectly the compiler may
or may not inline it dependent on optimization level and a failure
to inline an indirect call may or may not be diagnosed.

which matches how GCC behaves (last sentence)?

Corrections welcome (I am not a native speaker).


  parent reply	other threads:[~2014-07-15  9:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 18:15 [Bug web/61782] New: " daniel.santos at pobox dot com
2014-07-14 10:41 ` [Bug web/61782] " rguenth at gcc dot gnu.org
2014-07-14 15:34 ` daniel.santos at pobox dot com
2014-07-15  9:12 ` rguenth at gcc dot gnu.org [this message]
2014-07-15 10:17 ` redi at gcc dot gnu.org
2014-07-15 12:07 ` rguenth at gcc dot gnu.org
2014-07-15 19:52 ` daniel.santos at pobox dot com
2014-07-16  7:54 ` rguenth at gcc dot gnu.org
2014-07-16  7:54 ` rguenther at suse dot de
2014-07-16  7:54 ` rguenth at gcc dot gnu.org
2014-07-16 16:40 ` daniel.santos at pobox dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-61782-4-IhT42Tc2Fr@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).