public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Darrell.Wright at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/99006] New: make_shared<T[]> silently works Date: Mon, 08 Feb 2021 17:13:06 +0000 [thread overview] Message-ID: <bug-99006-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99006 Bug ID: 99006 Summary: make_shared<T[]> silently works Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: Darrell.Wright at gmail dot com Target Milestone: --- std::make_shared<T[]> in libstdc++ prior to c++20 doesn't fail. The minimal example is #include <memory> int func( ) { auto sp = std::make_shared<int[]>( 55 ); return *sp.get( ); } will return 55; libc++ removes it from the overload set and MS STL fails. https://gcc.godbolt.org/z/PaW6WY With T = int[], I think https://timsong-https://timsong-cpp.github.io/cppwp/n4659/util.smartptr.shared.create#1 should make this not work.
next reply other threads:[~2021-02-08 17:13 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-08 17:13 Darrell.Wright at gmail dot com [this message] 2021-02-09 8:08 ` [Bug libstdc++/99006] " redi at gcc dot gnu.org 2021-02-09 8:11 ` redi at gcc dot gnu.org 2021-04-22 13:33 ` redi at gcc dot gnu.org 2021-04-22 15:07 ` cvs-commit at gcc dot gnu.org 2021-05-11 19:50 ` cvs-commit at gcc dot gnu.org 2021-06-18 12:56 ` cvs-commit at gcc dot gnu.org 2021-06-18 14:43 ` cvs-commit at gcc dot gnu.org 2021-06-18 14:44 ` 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-99006-4@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).