public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jamagallon@able.es,
	nobody@gcc.gnu.org
Subject: Re: c++/9622: [3.2 regression] __PRETTY_FUNCTION__ incorrect in template dtors
Date: Sat, 08 Feb 2003 00:28:00 -0000	[thread overview]
Message-ID: <20030208002806.23733.qmail@sources.redhat.com> (raw)

Old Synopsis: __PRETTY_FUNCION__ incorrect in template dtors
New Synopsis: [3.2 regression] __PRETTY_FUNCTION__ incorrect in template dtors

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Sat Feb  8 00:28:06 2003
State-Changed-Why:
    Fixed in 3.3 and 3.4, not fixed in 3.2.2. Worked in 2.95:
    
    tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/c++ z.cc
    tmp/g> ./a.out
    A::A()
    B<T>::B() [with T = int]
    B<T>::~B() [with T = int]
    A::~A()
    
    tmp/g> /home/bangerth/bin/gcc-3.2.2-pre/bin/c++ z.cc
    tmp/g> ./a.out
    A::A()
    B<T>::B() [with T = int]
    void B<T>::B() [with T = int]
    A::~A()
    
    tmp/g> c++ z.cc
    tmp/g> ./a.out
    A::A()
    B<int>::B()
    B<int>::~B()
    A::~A()
    
    I think I recall that there was once a report in the bug
    database about this case. It may contain a clue as to
    what patch fixed this. If you want, it would be great
    if you could try to find this patch, and it might go
    into a possible gcc3.2.3, if such a release ever happens.
    
    Thanks 
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9622


             reply	other threads:[~2003-02-08  0:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08  0:28 bangerth [this message]
2003-02-08  7:36 Danny Smith
2003-04-25 21:14 jbuck

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=20030208002806.23733.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jamagallon@able.es \
    --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).