public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5390: Libiberty fails to demangle multi-digit template parameters.
Date: Mon, 10 Mar 2003 21:06:00 -0000 [thread overview]
Message-ID: <20030310210601.23178.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/5390; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Carlo Wood <carlo@alinoe.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/5390: Libiberty fails to demangle multi-digit template
parameters.
Date: Mon, 10 Mar 2003 15:03:05 -0600 (CST)
> > - gcc up to 2.95 has never generated the cases that your patch addresses
>
> It does. That is the whole point: 2.95 generates mangled names that are
> not supported, while the mangled names produces by older version ARE
> supported.
OK, thanks for the clarifications. I wasn't aware of this ABI change back
then.
> > The question thus is: if people are not overly interested in your patch
> > (which is regrettable, but apparently the case), then we can as well close
> > the PR. Since if we don't, we'll ask the same question again in a year,
> > and then people will care even less about 2.95.
> >
> > What's your opinion on this?
>
> The reason I filed the PR was because my library generated a mangled
> name that made libiberty core. As a library developer I *have* to
> support ALL versions of gcc(/libiberty) and was able to think of
> a workaround (somehow make sure that the template parameter constant
> where always < 10). It is never urgent for to have something fixed:
> I have to work with the current version (2.95.1 and up, all of them)
> anyway.
I understand these concerns. We build our library by 3 or 4 different
compilers and a total of 10 different versions or so :-(
> So, as far as I am concerned you can close this PR.
Does this still hold given DJ's mail?
> (Personally, I'd fix it though if I were you - but I am a perfectionist).
I might if I could. I have no knowledge of gcc, libiberty, etc at all. My
place is gnats, beyond that I can only try to get patch creators and
reviewers into contact -- usually a fruitless endeavor...
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ticam.utexas.edu
www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-03-10 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 21:06 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-11 20:06 DJ Delorie
2003-03-11 20:06 Wolfgang Bangerth
2003-03-11 2:26 Carlo Wood
2003-03-07 23:16 Carlo Wood
2003-03-07 17:26 DJ Delorie
2003-03-07 16:06 Wolfgang Bangerth
2003-03-07 12:36 Carlo Wood
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=20030310210601.23178.qmail@sources.redhat.com \
--to=bangerth@ticam.utexas.edu \
--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).