public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Carlo Wood <carlo@alinoe.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5390: Libiberty fails to demangle multi-digit template parameters.
Date: Fri, 07 Mar 2003 12:36:00 -0000	[thread overview]
Message-ID: <20030307123600.6849.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/5390; it has been noted by GNATS.

From: Carlo Wood <carlo@alinoe.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/5390: Libiberty fails to demangle multi-digit template parameters.
Date: Fri, 7 Mar 2003 13:14:20 +0100

 On Fri, Mar 07, 2003 at 02:26:50AM -0000, bangerth@dealii.org wrote:
 > Synopsis: Libiberty fails to demangle multi-digit template parameters.
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Fri Mar  7 02:26:50 2003
 > State-Changed-Why:
 >     Carlo, this report has been sitting idly for a year now.
 >     What is the present state? Is it still unsolved, or did
 >     your patch go in?
 >     
 >     Thanks
 >       Wolfgang
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5390
 
 
 I don't have 2.95.4 and don't even know if there is a CVS branch for it.
 
 The file libiberty/testsuite/demangle-expected still exists in version 3.3,
 and contains some broken mangled names (the way 2.95.x doesn't mangle them):
 my patch was not applied to 'libiberty/testsuite/demangle-expected' but it
 seems to have been partly applied, or someone did double work (and a bad job).
 
 c++filt of 3.3 does not demangle the correct mangled names (at least the
 ones I tried) - while it does demangle the old (wrong) mangled names.  By
 looking at libiberty/cplus-dem.c it seems that the patch was at least party
 applied, but someone made changes that broke it, or they ignored failing
 hunks.  As it is, libiberty/cplus-dem.c cannot demangle all the names as
 produced by 2.95.x.
 
 Because in the past my patches have been totally ignored too often, I did put
 this one in the bugs database, so it wouldn't get lost... But later I got so
 much demotivated that I unsubbed from all gcc mailinglists and stopped
 caring about gcc.  Therefore I must say now: I am sorry, but I can't bother
 to put more time into this one and fix it AGAIN - for the current cplus-dem.c.
 Perhaps you manage to manually fix the current cplus-dem.c by looking at
 the old patch and figuring out what was applied and what was not applied.
 Keep in mind that it is not possible, nor interesting to keep backwards
 compatibility with the mangled names as mangled by pre-2.95.x (the ones
 with a '-' in front of it in my testsuite/demangle-expected patch) in
 libiberty/testsuite/demangle-expected: if you do that then you garanteed
 have a broken demangler for the way 2.95.x mangles these names.  My patch
 (for cplus-dem.c) was the best possible fix imho.
 
 -- 
 Carlo Wood <carlo@alinoe.com>


             reply	other threads:[~2003-03-07 12:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 12:36 Carlo Wood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11 20:06 Wolfgang Bangerth
2003-03-11 20:06 DJ Delorie
2003-03-11  2:26 Carlo Wood
2003-03-10 21:06 Wolfgang Bangerth
2003-03-07 23:16 Carlo Wood
2003-03-07 17:26 DJ Delorie
2003-03-07 16:06 Wolfgang Bangerth
2003-03-07  2:26 bangerth

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=20030307123600.6849.qmail@sources.redhat.com \
    --to=carlo@alinoe.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).