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 libstdc++/107580] std::vector<std::string> parameter cannot be inferred with -D_GLIBCXX_USE_CXX11_ABI=0 Date: Wed, 09 Nov 2022 18:54:33 +0000 [thread overview] Message-ID: <bug-107580-4-0kc2qK4OXp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107580-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107580 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ABI Assignee|redi at gcc dot gnu.org |unassigned at gcc dot gnu.org Status|ASSIGNED |NEW --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- Unfortunately this changes the mangled name of the function, and so breaks the library ABI. Maybe that's why I didn't do it sooner. There are ways to solve that, but it's not as trivial as I thought.
prev parent reply other threads:[~2022-11-09 18:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-08 19:57 [Bug libstdc++/107580] New: std::vector<std::string> cannot be brace initialized " vyas.ramasubramani at gmail dot com 2022-11-08 22:21 ` [Bug libstdc++/107580] std::vector<std::string> parameter cannot be inferred " pinskia at gcc dot gnu.org 2022-11-09 4:30 ` redi at gcc dot gnu.org 2022-11-09 18:54 ` redi at gcc dot gnu.org [this message]
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-107580-4-0kc2qK4OXp@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).