public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/40459] g++.dg/abi/mangle*.C fail on darwin
Date: Wed, 16 Dec 2009 20:29:00 -0000 [thread overview]
Message-ID: <20091216202918.18052.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40459-12313@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
------- Comment #8 from howarth at nitro dot med dot uc dot edu 2009-12-16 20:29 -------
What's up with the instantiation portions of the warning messages in darwin? On
Fedora 10, gcc trunk shows...
~/dist/bin/g++ mangle11.C -nostdinc++ -fmessage-length=0 -Wabi -fabi-version=1
-S -o mangle11.s
mangle11.C:10:24: warning: the mangled name of ‘void f(typename Q::X) [with Q =
S, typename Q::X = int]’ will change in a future version of GCC
whereas on darwin with gcc-4..4.2 we get...
g++-4 mangle11.C -nostdinc++ -fmessage-length=0 -Wabi -fabi-version=1 -S -o
mangle11.s
mangle11.C: In instantiation of ‘void f(typename Q::X) [with Q = S]’:
mangle11.C:10: instantiated from here
mangle11.C:4: warning: the mangled name of ‘void f(typename Q::X) [with Q = S]’
will change in a future version of GCC
which is exactly what I see with g++-4.3.2 on Fedora 10.
g++ mangle11.C -nostdinc++ -fmessage-length=0 -Wabi -fabi-version=1 -S -o
mangle11.s
mangle11.C: In instantiation of ‘void f(typename Q::X) [with Q = S]’:
mangle11.C:10: instantiated from here
mangle11.C:4: warning: the mangled name of ‘void f(typename Q::X) [with Q = S]’
will change in a future version of GCC
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40459
next prev parent reply other threads:[~2009-12-16 20:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 12:48 [Bug testsuite/40459] New: " dominiq at lps dot ens dot fr
2009-07-20 3:08 ` [Bug testsuite/40459] " howarth at nitro dot med dot uc dot edu
2009-07-27 14:02 ` howarth at nitro dot med dot uc dot edu
2009-09-27 3:43 ` howarth at nitro dot med dot uc dot edu
2009-12-15 1:56 ` howarth at nitro dot med dot uc dot edu
2009-12-16 13:59 ` howarth at nitro dot med dot uc dot edu
2009-12-16 14:12 ` jason at gcc dot gnu dot org
2009-12-16 14:32 ` howarth at nitro dot med dot uc dot edu
2009-12-16 20:29 ` howarth at nitro dot med dot uc dot edu [this message]
2009-12-16 22:19 ` howarth at nitro dot med dot uc dot edu
2009-12-17 18:09 ` espindola at gcc dot gnu dot org
2009-12-17 19:16 ` dominiq at lps dot ens dot fr
2009-12-22 18:29 ` howarth at nitro dot med dot uc dot edu
2010-03-01 0:23 ` mikestump at comcast dot net
2010-03-01 10:20 ` dominiq at lps dot ens dot fr
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=20091216202918.18052.qmail@sourceware.org \
--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).