public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111300] [14 Regression] g++.dg/modules/xtreme-header_b.C Date: Sat, 09 Sep 2023 19:58:02 +0000 [thread overview] Message-ID: <bug-111300-4-uGOIbmWx3s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111300-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111300 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- Possibly relevant, compiling anything including <stacktrace> with -Wsystem-headers -Wabi gives these warnings: /home/jwakely/gcc/13/include/c++/13.2.1/stacktrace: At global scope: /home/jwakely/gcc/13/include/c++/13.2.1/stacktrace:201:24: warning: the mangled name of 'constexpr std::stacktrace_entry::_M_get_info(std::string*, std::string*, int*) const::<lambda(void*, std::stacktrace_entry::uintptr_t, const char*, std::stacktrace_entry::uintptr_t, std::stacktrace_entry::uintptr_t)>::operator void (*)(void*, std::stacktrace_entry::uintptr_t, const char*, std::stacktrace_entry::uintptr_t, std::stacktrace_entry::uintptr_t)() const' changed between '-fabi-version=10' ('_ZZNKSt16stacktrace_entry11_M_get_infoEPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_PiENKUlPvmPKcmmE0_cvPFvS8_mSA_mmEEv') and '-fabi-version=18' ('_ZZNKSt16stacktrace_entry11_M_get_infoEPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_PiENKUlPvmPKcmmE_cvPFvS8_mSA_mmEEv') [-Wabi] 201 | auto __cb2 = [](void* __data, uintptr_t, const char* __symname, | ^ /home/jwakely/gcc/13/include/c++/13.2.1/stacktrace:201:24: warning: the mangled name of 'static constexpr void std::stacktrace_entry::_M_get_info(std::string*, std::string*, int*) const::<lambda(void*, std::stacktrace_entry::uintptr_t, const char*, std::stacktrace_entry::uintptr_t, std::stacktrace_entry::uintptr_t)>::_FUN(void*, std::stacktrace_entry::uintptr_t, const char*, std::stacktrace_entry::uintptr_t, std::stacktrace_entry::uintptr_t)' changed between '-fabi-version=10' ('_ZZNKSt16stacktrace_entry11_M_get_infoEPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_PiENUlPvmPKcmmE0_4_FUNES8_mSA_mm') and '-fabi-version=18' ('_ZZNKSt16stacktrace_entry11_M_get_infoEPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_PiENUlPvmPKcmmE_4_FUNES8_mSA_mm') [-Wabi] /home/jwakely/gcc/13/include/c++/13.2.1/stacktrace:201:24: warning: the mangled name of 'std::stacktrace_entry::_M_get_info(std::string*, std::string*, int*) const::<lambda(void*, std::stacktrace_entry::uintptr_t, const char*, std::stacktrace_entry::uintptr_t, std::stacktrace_entry::uintptr_t)>' changed between '-fabi-version=10' ('_ZZNKSt16stacktrace_entry11_M_get_infoEPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_PiENKUlPvmPKcmmE0_clES8_mSA_mm') and '-fabi-version=18' ('_ZZNKSt16stacktrace_entry11_M_get_infoEPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_PiENKUlPvmPKcmmE_clES8_mSA_mm') [-Wabi] e.g. g++ -x c++ /dev/null -include stacktrace -Wsystem-headers -std=c++23 -Wabi=10 (either using GCC 13 built with --enable-libstdcxx-backtrace or using GCC trunk before r14-3812-gb96b554592c5cb which moved the lambda out of the header into libstdc++exp.a) Those -Wabi warnings might be related to the "previous mangle" errors in the modules test.
next prev parent reply other threads:[~2023-09-09 19:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-06 2:44 [Bug c++/111300] New: [14 Regression] g++.dg/modules/xtreme-header-2_b.C hp at gcc dot gnu.org 2023-09-06 13:40 ` [Bug c++/111300] [14 Regression] g++.dg/modules/xtreme-header_b.C redi at gcc dot gnu.org 2023-09-09 13:37 ` redi at gcc dot gnu.org 2023-09-09 19:58 ` redi at gcc dot gnu.org [this message] 2023-09-09 21:39 ` hp at gcc dot gnu.org 2023-09-09 21:41 ` hp at gcc dot gnu.org 2023-09-10 9:15 ` [Bug c++/111300] Modules error: mangling of [lambda] conflicts with previous mangle redi at gcc dot gnu.org 2023-09-10 9:24 ` redi 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-111300-4-uGOIbmWx3s@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).