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 c++/102576] [modules] Importing <initializer_list> doesn't permit implicit uses Date: Thu, 29 Sep 2022 20:27:50 +0000 [thread overview] Message-ID: <bug-102576-4-ypIKzTR0ya@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102576-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102576 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:c2ee70f20de8133a88553270073226b0f3f55f62 commit r13-2969-gc2ee70f20de8133a88553270073226b0f3f55f62 Author: Patrick Palka <ppalka@redhat.com> Date: Thu Sep 29 16:27:30 2022 -0400 c++: implicit lookup of std::initializer_list [PR102576] Here the lookup for the implicit use of std::initializer_list fails because we do it using get_namespace_binding, which isn't import aware. Fix this by using lookup_qualified_name instead. PR c++/102576 gcc/cp/ChangeLog: * pt.cc (listify): Use lookup_qualified_name instead of get_namespace_binding. gcc/testsuite/ChangeLog: * g++.dg/modules/pr102576_a.H: New test. * g++.dg/modules/pr102576_b.C: New test.
next prev parent reply other threads:[~2022-09-29 20:27 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-03 14:24 [Bug c++/102576] New: " johelegp at gmail dot com 2021-10-03 14:37 ` [Bug c++/102576] " johelegp at gmail dot com 2022-09-29 20:27 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-29 20:28 ` ppalka at gcc dot gnu.org 2023-03-27 12:55 ` ppalka 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-102576-4-ypIKzTR0ya@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).