public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pedro at palves dot net" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/29138] [gdb/testsuite] FAIL: gdb.cp/break-f-std-string.exp: _GLIBCXX_USE_CXX11_ABI=1: whatis /r std::string Date: Wed, 11 May 2022 12:36:51 +0000 [thread overview] Message-ID: <bug-29138-4717-A7IK0pIGpC@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29138-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29138 Pedro Alves <pedro at palves dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pedro at palves dot net --- Comment #3 from Pedro Alves <pedro at palves dot net> --- Sounds like it, yes. Thanks tracking that down. I'm not sure off hand what is the best fix. I mean, it's probably something around skipping the test for gcc < 8 (C++11 ABI support was added around GCC 5 IIRC, but older ones should just test the same thing twice so pointless to let them run the _GLIBCXX_USE_CXX11_ABI=1 tests) or something. Or maybe the testcase .cc file could define std::string typedef itself on such compilers. We could test std::__cxx11::string too, though that wouldn't exercise the original issue the testcase ran into, with the special mangling feature for "std::string", so seems a bit pointless too. Or something else. In any case, it doesn't look like a GDB bug. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-05-11 12:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-10 14:57 [Bug testsuite/29138] New: " vries at gcc dot gnu.org 2022-05-10 15:22 ` [Bug testsuite/29138] " vries at gcc dot gnu.org 2022-05-10 16:26 ` vries at gcc dot gnu.org 2022-05-11 12:36 ` pedro at palves dot net [this message] 2022-05-11 12:37 ` pedro at palves dot net 2022-05-12 11:47 ` vries at gcc dot gnu.org 2022-05-12 13:01 ` vries 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-29138-4717-A7IK0pIGpC@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).