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++/111511] Incorrect ADL in std::to_array in GCC 11/12/13 Date: Wed, 27 Sep 2023 16:21:48 +0000 [thread overview] Message-ID: <bug-111511-4-LsIFb1MZDR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111511-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111511 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:97a33ab114187e7c6cd6c6c0f06cd8225e8aeef5 commit r11-11021-g97a33ab114187e7c6cd6c6c0f06cd8225e8aeef5 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Sep 21 09:14:57 2023 +0100 libstdc++: Prevent unwanted ADL in std::to_array [PR111512] Qualify the calls to the __to_array helper to prevent ADL, so we don't try to complete associated classes. libstdc++-v3/ChangeLog: PR libstdc++/111511 PR c++/111512 * include/std/array (to_array): Qualify calls to __to_array. * testsuite/23_containers/array/creation/111512.cc: New test. (cherry picked from commit 77cf3773021b0a20d89623e09d620747a05588ec)
next prev parent reply other threads:[~2023-09-27 16:21 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-21 6:17 [Bug libstdc++/111511] New: " de34 at live dot cn 2023-09-21 8:03 ` [Bug libstdc++/111511] " redi at gcc dot gnu.org 2023-09-21 10:33 ` m.cencora at gmail dot com 2023-09-21 10:42 ` redi at gcc dot gnu.org 2023-09-21 10:45 ` m.cencora at gmail dot com 2023-09-21 11:37 ` de34 at live dot cn 2023-09-25 8:53 ` cvs-commit at gcc dot gnu.org 2023-09-26 20:15 ` cvs-commit at gcc dot gnu.org 2023-09-26 22:55 ` cvs-commit at gcc dot gnu.org 2023-09-27 16:21 ` cvs-commit at gcc dot gnu.org [this message] 2023-09-27 16:23 ` 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-111511-4-LsIFb1MZDR@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).