public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/61321] demangler crash on casts in template parameters
Date: Mon, 26 May 2014 15:33:00 -0000	[thread overview]
Message-ID: <bug-61321-4-mCG9sFtbEj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61321-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
I think we need to distinguish conversion operators from expression casts.  

Working on a patch that adds:

--- c/include/demangle.h
+++ w/include/demangle.h
@@ -373,6 +373,10 @@ enum demangle_component_type
   /* A typecast, represented as a unary operator.  The one subtree is
      the type to which the argument should be cast.  */
   DEMANGLE_COMPONENT_CAST,
+  /* A conversion operator, represented as a unary operator.  The one
+     subtree is the type to which the argument should be converted
+     to.  */
+  DEMANGLE_COMPONENT_CONVERSION,


  reply	other threads:[~2014-05-26 15:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 14:03 [Bug other/61321] New: " palves at redhat dot com
2014-05-26 15:33 ` palves at redhat dot com [this message]
2014-05-26 16:40 ` [Bug other/61321] " palves at redhat dot com
2014-05-26 20:52 ` redi at gcc dot gnu.org
2014-05-27 12:00 ` palves at redhat dot com
2014-11-10 19:01 ` ccoutant at gcc dot gnu.org
2014-11-10 19:19 ` ccoutant at gcc dot gnu.org
2015-07-06  4:56 ` trippels at gcc dot gnu.org
2015-07-06  5:14 ` trippels at gcc dot gnu.org
2015-07-14  9:39 ` palves at redhat dot com
2015-07-27 10:09 ` trippels at gcc dot gnu.org
2015-08-18 23:11 ` miyuki 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-61321-4-mCG9sFtbEj@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).