public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/103086] [11 Regression] std::unique_ptr printer gets confused by [[no_unique_address]] in tuple Date: Wed, 05 Jan 2022 17:53:49 +0000 [thread overview] Message-ID: <bug-103086-4-2LnRcd5cwZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103086-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103086 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:865ad53c49953f2950901aaf45b34a38841df019 commit r10-10375-g865ad53c49953f2950901aaf45b34a38841df019 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Nov 23 21:35:40 2021 +0000 libstdc++: Add another testcase for std::unique_ptr printer [PR103086] libstdc++-v3/ChangeLog: PR libstdc++/103086 * testsuite/libstdc++-prettyprinters/cxx11.cc: Check unique_ptr with non-empty pointer and non-empty deleter. (cherry picked from commit c59ec55c3459fba619e05ee7f59480b71e85ffd7)
next prev parent reply other threads:[~2022-01-05 17:53 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-04 17:29 [Bug libstdc++/103086] New: [11/12 " redi at gcc dot gnu.org 2021-11-04 17:29 ` [Bug libstdc++/103086] " redi at gcc dot gnu.org 2021-11-04 21:30 ` redi at gcc dot gnu.org 2021-11-04 23:06 ` cvs-commit at gcc dot gnu.org 2021-11-04 23:10 ` redi at gcc dot gnu.org 2021-11-05 7:24 ` [Bug libstdc++/103086] [11 " rguenth at gcc dot gnu.org 2021-11-23 17:33 ` redi at gcc dot gnu.org 2021-11-23 21:18 ` cvs-commit at gcc dot gnu.org 2021-11-23 21:18 ` redi at gcc dot gnu.org 2021-11-23 21:41 ` cvs-commit at gcc dot gnu.org 2021-11-24 11:50 ` cvs-commit at gcc dot gnu.org 2022-01-05 17:53 ` cvs-commit at gcc dot gnu.org 2022-01-05 17:53 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-05 17:56 ` 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-103086-4-2LnRcd5cwZ@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).