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++/116529] Construction of unique_ptr with reference type is rejected because of auto_ptr constructor Date: Thu, 29 Aug 2024 10:17:48 +0000 [thread overview] Message-ID: <bug-116529-4-VLZUxWDNiZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-116529-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116529 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- -D_GLIBCXX_USE_DEPRECATED=0 allows it to compile
next prev parent reply other threads:[~2024-08-29 10:17 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-08-29 6:24 [Bug libstdc++/116529] New: " luigighiron at gmail dot com 2024-08-29 10:17 ` redi at gcc dot gnu.org [this message] 2024-08-29 10:22 ` [Bug libstdc++/116529] " redi at gcc dot gnu.org 2024-08-29 10:24 ` redi at gcc dot gnu.org 2024-08-30 10:43 ` redi at gcc dot gnu.org 2024-08-30 18:45 ` luigighiron at gmail dot com 2024-09-03 10:08 ` de34 at live dot cn 2024-09-03 13:45 ` redi at gcc dot gnu.org 2024-09-03 13:46 ` redi at gcc dot gnu.org 2024-09-20 22:50 ` cvs-commit at gcc dot gnu.org 2024-09-23 19:24 ` cvs-commit 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-116529-4-VLZUxWDNiZ@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).