public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/108470] Missing documentation for alternate uses of __attribute__((noinline))
Date: Thu, 18 Jan 2024 23:26:57 +0000	[thread overview]
Message-ID: <bug-108470-4-oeNLLADFZv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108470-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Sandra Loosemore <sandra@gcc.gnu.org>:

https://gcc.gnu.org/g:9b6b7d615543d73381cb1f994825d9bca024c838

commit r14-8261-g9b6b7d615543d73381cb1f994825d9bca024c838
Author: Sandra Loosemore <sandra@codesourcery.com>
Date:   Thu Jan 18 23:19:39 2024 +0000

    Improve documentation of noinline and noipa attributes [PR108470]

    gcc/ChangeLog
            PR ipa/108470
            * doc/extend.texi (Common Function Attributes): Document that
            noinline also disables some interprocedural optimizations and
            improve flow to the part about using inline asm instead to
            disable calls from being optimized away completely.  Remove the
            sentence that says noipa is mainly for internal compiler testing.

  parent reply	other threads:[~2024-01-18 23:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 20:48 [Bug ipa/108470] New: " rth at gcc dot gnu.org
2023-01-20  8:30 ` [Bug ipa/108470] " rguenth at gcc dot gnu.org
2023-02-09 11:40 ` marxin at gcc dot gnu.org
2023-02-09 11:53 ` rearnsha at gcc dot gnu.org
2023-02-09 12:46 ` marxin at gcc dot gnu.org
2024-01-18 23:26 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-18 23:28 ` sandra at gcc dot gnu.org
2024-01-20 17:22 ` pinskia at gcc dot gnu.org

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-108470-4-oeNLLADFZv@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).