public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8964: [3.3 regression] [ABI] different mangling of names
Date: Mon, 23 Dec 2002 09:46:00 -0000	[thread overview]
Message-ID: <20021223174602.5468.qmail@sources.redhat.com> (raw)

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

From: Janis Johnson <janis187@us.ibm.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, catherin@ca.ibm.com,
   gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/8964: [3.3 regression] [ABI] different mangling of names
Date: Mon, 23 Dec 2002 09:42:19 -0800

 PR c++/8964 reports a change in name mangling that is not
 affected by the --abi-version switch.  It's caused by this
 patch, which adds a -Wabi warning that is issued for this
 test case, and information to the documentation about this
 kind of code.
 
 Should the name mangling here be affected by --abi-version?
 
 --- gcc/gcc/ChangeLog ---
 
 2002-10-03  Mark Mitchell  <mark@codesourcery.com>
 
         * doc/invoke.texi (-Wabi): Document mangling bug.
 
 --- gcc/gcc/cp/ChangeLog ---
 
 2002-10-03  Mark Mitchell  <mark@codesourcery.com>
 
         PR c++/8006
         * mangle.c (CLASSTYPE_TEMPLATE_ID_P): Handle
         instances of template template parameters.
 
 My testing used the submitter's test case.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8964
 
 
 


             reply	other threads:[~2002-12-23 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23  9:46 Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-16 13:10 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=20021223174602.5468.qmail@sources.redhat.com \
    --to=janis187@us.ibm.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).