public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49015] [C++0x] Non-defining constexpr function declarations require complete argument/return types
Date: Wed, 18 May 2011 17:38:00 -0000	[thread overview]
Message-ID: <bug-49015-4-xf8XfltcRA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49015-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49015

--- Comment #1 from Jason Merrill <jason at gcc dot gnu.org> 2011-05-18 17:19:19 UTC ---
Author: jason
Date: Wed May 18 17:19:15 2011
New Revision: 173869

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173869
Log:
    PR c++/48948
    PR c++/49015
    * class.c (finalize_literal_type_property): Do check
    for constexpr member functions of non-literal class.
    (finish_struct): Don't call check_deferred_constexpr_decls.
    * cp-tree.h: Don't declare it.
    (DECL_DEFERRED_CONSTEXPR_CHECK): Remove.
    * decl.c (grok_special_member_properties): Don't check it
    (grokfnedcl): Don't call validate_constexpr_fundecl.
    (start_preparsed_function): Do call it.
    * pt.c (tsubst_decl): Don't call it.
    (instantiate_class_template_1): Don't call
    check_deferred_constexpr_decls.
    * semantics.c (literal_type_p): Check for any incompleteness.
    (ensure_literal_type_for_constexpr_object): Likewise.
    (is_valid_constexpr_fn): Revert deferral changes.
    (validate_constexpr_fundecl): Likewise.
    (register_constexpr_fundef): Likewise.
    (check_deferred_constexpr_decls): Remove.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-incomplete3.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/class.c
    trunk/gcc/cp/cp-tree.h
    trunk/gcc/cp/decl.c
    trunk/gcc/cp/pt.c
    trunk/gcc/cp/semantics.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-incomplete2.C
    trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-memfn1.C


  reply	other threads:[~2011-05-18 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 21:40 [Bug c++/49015] New: " daniel.kruegler at googlemail dot com
2011-05-18 17:38 ` jason at gcc dot gnu.org [this message]
2011-05-18 18:00 ` [Bug c++/49015] " jason 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-49015-4-xf8XfltcRA@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).