public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/4926] C++ ABI needs clarification on mangling of complex expressions Date: Wed, 03 Feb 2010 20:43:00 -0000 [thread overview] Message-ID: <20100203204326.3749.qmail@sourceware.org> (raw) In-Reply-To: <bug-4926-2734@http.gcc.gnu.org/bugzilla/> ------- Comment #15 from jason at gcc dot gnu dot org 2010-02-03 20:43 ------- Subject: Bug 4926 Author: jason Date: Wed Feb 3 20:42:48 2010 New Revision: 156482 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=156482 Log: PR c++/4926 PR c++/38600 * mangle.c (write_unqualified_id): Split out from write_expression. (write_unqualified_name): Call it. (write_member_name): Likewise. (write_expression): Support TEMPLATE_ID_EXPR. Disambiguate operator names. Added: trunk/gcc/testsuite/g++.dg/abi/mangle35.C trunk/gcc/testsuite/g++.dg/abi/mangle37.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/mangle.c trunk/gcc/testsuite/ChangeLog trunk/libiberty/ChangeLog trunk/libiberty/cp-demangle.c trunk/libiberty/testsuite/demangle-expected -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=4926
prev parent reply other threads:[~2010-02-03 20:43 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-4926-2734@http.gcc.gnu.org/bugzilla/> 2009-03-03 21:18 ` jason at gcc dot gnu dot org 2009-03-28 20:55 ` reichelt at gcc dot gnu dot org 2009-03-28 23:23 ` hjl dot tools at gmail dot com 2009-04-01 16:12 ` hjl dot tools at gmail dot com 2009-04-01 16:22 ` paolo dot carlini at oracle dot com 2009-04-01 18:10 ` hjl at gcc dot gnu dot org 2009-04-01 18:11 ` hjl at gcc dot gnu dot org 2009-04-01 18:13 ` hjl dot tools at gmail dot com 2009-04-06 15:39 ` jason at redhat dot com 2009-04-21 16:02 ` jakub at gcc dot gnu dot org 2009-07-22 10:32 ` jakub at gcc dot gnu dot org 2009-10-15 12:58 ` jakub at gcc dot gnu dot org 2009-11-12 4:57 ` jason at gcc dot gnu dot org 2010-02-03 20:43 ` jason at gcc dot gnu dot org [this message]
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=20100203204326.3749.qmail@sourceware.org \ --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).