public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55250] [C++0x] enum declarations within constexpr function are allowed, constexpr declarations are not
Date: Mon, 06 Oct 2014 16:14:00 -0000	[thread overview]
Message-ID: <bug-55250-4-vQWypKR3DV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55250-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> ---
Author: paolo
Date: Mon Oct  6 16:13:41 2014
New Revision: 215954

URL: https://gcc.gnu.org/viewcvs?rev=215954&root=gcc&view=rev
Log:
/cp
2014-10-06  Paolo Carlini  <paolo.carlini@oracle.com>

    PR c++/55250
    * semantics.c (check_constexpr_bind_expr_vars): New.
    (check_constexpr_ctor_body, massage_constexpr_body): Use it.
    (build_constexpr_constructor_member_initializers): Handle
    BIND_EXPR in the main conditional.

/testsuite
2014-10-06  Paolo Carlini  <paolo.carlini@oracle.com>

    PR c++/55250
    * g++.dg/cpp0x/constexpr-type-decl1.C: New.
    * g++.dg/cpp0x/constexpr-type-def1.C: Likewise.
    * g++.dg/cpp1y/constexpr-type-def1.C: Likewise.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-type-decl1.C
    trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-type-def1.C
    trunk/gcc/testsuite/g++.dg/cpp1y/constexpr-type-def1.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/semantics.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2014-10-06 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 12:28 [Bug c++/55250] New: [C++0x][constexpr] " bisqwit at iki dot fi
2012-11-09 12:52 ` [Bug c++/55250] " redi at gcc dot gnu.org
2014-10-06 16:14 ` paolo at gcc dot gnu.org [this message]
2014-10-06 16:16 ` [Bug c++/55250] [C++0x] " paolo.carlini at oracle 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-55250-4-vQWypKR3DV@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).