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 libstdc++/99985] [9/10/11 Regression] bits/hashtable.h:483:9: error: body of ‘constexpr’ function ... not a return-statement since g:1cbba49e3417d9b0661e70301d6fb7a7f52fd360
Date: Fri, 09 Apr 2021 12:09:45 +0000	[thread overview]
Message-ID: <bug-99985-4-NxHmRXIisX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99985-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:40ccb47b505b528244ee305923681c0ae3b6f4d5

commit r11-8085-g40ccb47b505b528244ee305923681c0ae3b6f4d5
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Apr 9 12:05:39 2021 +0100

    libstdc++: Fix invalid constexpr function in C++11 mode [PR 99985]

    I keep forgetting that a constexpr function in C++11 has to be a single
    return statement.

    libstdc++-v3/ChangeLog:

            PR libstdc++/99985
            * include/bits/hashtable.h (_Hashtable::_S_nothrow_move()): Fix
            to be a valid constexpr function in C++11.
            * testsuite/23_containers/unordered_set/cons/99985.cc: New test.

  parent reply	other threads:[~2021-04-09 12:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  8:34 [Bug c++/99985] New: [11 " marxin at gcc dot gnu.org
2021-04-09  8:35 ` [Bug c++/99985] " marxin at gcc dot gnu.org
2021-04-09 10:06 ` jakub at gcc dot gnu.org
2021-04-09 10:21 ` [Bug c++/99985] [10/11 " redi at gcc dot gnu.org
2021-04-09 10:24 ` redi at gcc dot gnu.org
2021-04-09 10:27 ` jakub at gcc dot gnu.org
2021-04-09 10:29 ` redi at gcc dot gnu.org
2021-04-09 12:09 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-09 15:15 ` [Bug libstdc++/99985] [9/10/11 " cvs-commit at gcc dot gnu.org
2021-04-09 16:42 ` cvs-commit at gcc dot gnu.org
2021-04-09 16:42 ` redi 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-99985-4-NxHmRXIisX@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).