public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-5346] doc: document -fimplicit-constexpr
Date: Wed, 17 Nov 2021 17:45:35 +0000 (GMT)	[thread overview]
Message-ID: <20211117174535.36BD9385AC32@sourceware.org> (raw)

https://gcc.gnu.org/g:d3a9082d7acc3ef443de6f14a16e7063d92844b1

commit r12-5346-gd3a9082d7acc3ef443de6f14a16e7063d92844b1
Author: Jason Merrill <jason@redhat.com>
Date:   Wed Nov 17 05:45:02 2021 -0500

    doc: document -fimplicit-constexpr
    
    I forgot this in the implementation patch.
    
    gcc/ChangeLog:
    
            * doc/invoke.texi (C++ Dialect Options): Document
            -fimplicit-constexpr.

Diff:
---
 gcc/doc/invoke.texi | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index a22758d18ee..bd6b9f6010c 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -3106,6 +3106,13 @@ word as an identifier.  You can use the keyword @code{__typeof__} instead.
 This option is implied by the strict ISO C++ dialects: @option{-ansi},
 @option{-std=c++98}, @option{-std=c++11}, etc.
 
+@item -fimplicit-constexpr
+@opindex fimplicit-constexpr
+Make inline functions implicitly constexpr, if they satisfy the
+requirements for a constexpr function.  This option can be used in
+C++14 mode or later.  This can result in initialization changing from
+dynamic to static and other optimizations.
+
 @item -fno-implicit-templates
 @opindex fno-implicit-templates
 @opindex fimplicit-templates


                 reply	other threads:[~2021-11-17 17:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211117174535.36BD9385AC32@sourceware.org \
    --to=jason@gcc.gnu.org \
    --cc=gcc-cvs@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).