public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlo at alinoe dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/12843] [ABI] Possibly wrong mangling (incompatibility with icc7)
Date: Thu, 30 Oct 2003 16:19:00 -0000 [thread overview]
Message-ID: <20031030161227.7090.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031030142910.12843.bangerth@dealii.org>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12843
------- Additional Comments From carlo at alinoe dot com 2003-10-30 16:12 -------
Subject: Re: [ABI] Possibly wrong mangling (incompatibility with icc7)
On Thu, Oct 30, 2003 at 02:41:10PM -0000, nathan at gcc dot gnu dot org wrote:
> The icc manglings and fabi-version=1 are definitly wrong. The name
> of a template parameter should never appear in a mangling. The fabi=2
> mangling looks good to me
> 1f -- func name
> I1XE template arg list. arg is 1X
> NT_ 8iteratorE - nested name using first template arg :: iterator
> S1_ copy of substitution 1
>
> defect in icc
This is probably because the ABI was changed since it publication
one or two years ago.
<nested-name> ::= N [<CV-qualifiers>] <prefix> <unqualified-name> E
::= N [<CV-qualifiers>] <template-prefix> <template-args> E
<prefix> ::= <prefix> <unqualified-name>
::= <template-prefix> <template-args>
::= <template-param> <== NEW
::= # empty
::= <substitution>
<template-prefix> ::= <prefix> <template unqualified-name>
::= <template-param> <== NEW
::= <substitution>
Those <template-param> were not there in the beginning.
This also reveals a bug in the demangler.
I guess I'll have to go over the most recent specification to check
what all was changed.
next prev parent reply other threads:[~2003-10-30 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 14:41 [Bug c++/12843] New: " bangerth at dealii dot org
2003-10-30 14:42 ` [Bug c++/12843] " nathan at gcc dot gnu dot org
2003-10-30 16:12 ` Carlo Wood
2003-10-30 15:58 ` bangerth at ices dot utexas dot edu
2003-10-30 16:19 ` carlo at alinoe dot com [this message]
2004-07-13 20:27 ` reichelt at gcc dot gnu dot org
2004-07-13 20:27 ` reichelt at gcc dot gnu dot 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=20031030161227.7090.qmail@sources.redhat.com \
--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).