public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/51365] cannot use final empty class in std::tuple Date: Thu, 15 Dec 2011 10:06:00 -0000 [thread overview] Message-ID: <bug-51365-4-xo7LGegk3s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51365-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51365 --- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-12-15 10:02:50 UTC --- Author: redi Date: Thu Dec 15 10:02:45 2011 New Revision: 182360 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=182360 Log: c-family: PR libstdc++/51365 * c-common.c (RID_IS_FINAL): Add. * c-common.h (RID_IS_FINAL): Add. cp: PR libstdc++/51365 * cp-tree.h (CPTK_IS_FINAL): Add. * parser.c (cp_parser_translation_unit): Handle RID_IS_FINAL. (cp_parser_primary_expression, cp_parser_trait_expr): Likewise. * semantics.c (trait_expr_value, finish_trait_expr): Handle CPTK_IS_FINAL. * cxx-pretty-print.c (pp_cxx_trait_expression): Likewise. testsuite: PR libstdc++/51365 * g++.dg/ext/is_final.C: New. Added: trunk/gcc/testsuite/g++.dg/ext/is_final.C Modified: trunk/gcc/c-family/ChangeLog trunk/gcc/c-family/c-common.c trunk/gcc/c-family/c-common.h trunk/gcc/cp/ChangeLog trunk/gcc/cp/cp-tree.h trunk/gcc/cp/cxx-pretty-print.c trunk/gcc/cp/parser.c trunk/gcc/cp/semantics.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2011-12-15 10:03 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-30 19:22 [Bug libstdc++/51365] New: " redi at gcc dot gnu.org 2011-11-30 19:34 ` [Bug libstdc++/51365] " redi at gcc dot gnu.org 2011-11-30 19:40 ` paolo.carlini at oracle dot com 2011-11-30 21:26 ` redi at gcc dot gnu.org 2011-11-30 21:30 ` redi at gcc dot gnu.org 2011-11-30 21:30 ` redi at gcc dot gnu.org 2011-11-30 23:51 ` redi at gcc dot gnu.org 2011-12-01 1:07 ` redi at gcc dot gnu.org 2011-12-03 12:06 ` redi at gcc dot gnu.org 2011-12-11 12:55 ` marc.glisse at normalesup dot org 2011-12-11 13:51 ` redi at gcc dot gnu.org 2011-12-11 13:56 ` marc.glisse at normalesup dot org 2011-12-15 10:06 ` redi at gcc dot gnu.org [this message] 2011-12-15 10:10 ` redi at gcc dot gnu.org 2011-12-20 9:14 ` redi at gcc dot gnu.org 2012-02-04 13:54 ` redi at gcc dot gnu.org 2013-03-22 14:45 ` jakub at gcc dot gnu.org 2013-04-28 11:40 ` redi at gcc dot gnu.org 2014-04-22 11:36 ` jakub at gcc dot gnu.org 2014-04-22 14:36 ` 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-51365-4-xo7LGegk3s@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: linkBe 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).