public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51804] New: Wabi false positives Date: Mon, 09 Jan 2012 21:26:00 -0000 [thread overview] Message-ID: <bug-51804-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51804 Bug #: 51804 Summary: Wabi false positives Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: bkoz@gcc.gnu.org When adding -Wabi to the libstdc++ build flags, I ran the testsuite with -Wabi as well, since that tends to instantiate more templates than just building the libstdc++.so. When I run the the libstdc++ testsuite with -Wabi, I get 72 new fails. Some of these make sense from the manual, ie http://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#C_002b_002b-Dialect-Options or from the example with non-type reference extern int N; template <int &> struct S {}; void n(S<N>) {2;} which is -fabi-version=3 0000000000000000 T _Z1n1SIL_Z1NEE -fabi-version=2 0000000000000000 T _Z1n1SILZ1NEE 0000000000000000 T _Z1n1SIL_Z1NEE One can see the difference very easily in terms of what is produced by the compiler. However, there look to be some false positives, in things like: libstdc++-v3/testsuite/20_util/tuple/cons/constexpr-2.cc and others (full log attached as 20120109-libstdc++.sum.bz2) I see a lot of things like: s.h:752:7: warning: the mangled name of ‘void __gnu_test::constexpr_single_value_constructible::_Concept<_Ttesttype, _Tvaluetype, true>::__constraint() [with _Ttesttype = std::tuple<int, int>; _Tvaluetype = std::tuple<short int, short int>]’ will change in a future version of GCC [-Wabi] I'm finding it harder to make sense of this warning. Is this a false positive? If not, what changed? I'll attach a pre-processed file that gives this warning, and a log of the test run.
next reply other threads:[~2012-01-09 21:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-09 21:26 bkoz at gcc dot gnu.org [this message] 2012-01-09 21:27 ` [Bug c++/51804] " bkoz at gcc dot gnu.org 2012-01-09 21:44 ` bkoz at gcc dot gnu.org 2012-01-09 21:46 ` bkoz at gcc dot gnu.org 2012-01-09 22:22 ` jason at gcc dot gnu.org 2012-01-10 0:06 ` bkoz at gcc dot gnu.org 2012-01-11 4:23 ` [Bug c++/51804] -Wabi confusion bkoz at gcc dot gnu.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=bug-51804-4@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).