This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/39982] Fail to use constructor to initialize volatile declaration (no matching function for call)
- From: "msebor at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 16 Mar 2017 00:14:13 +0000
- Subject: [Bug c++/39982] Fail to use constructor to initialize volatile declaration (no matching function for call)
- Auto-submitted: auto-generated
- References: <bug-39982-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39982
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |RESOLVED
CC| |msebor at gcc dot gnu.org
Known to work| |4.9.0, 5.3.0, 6.3.0, 7.0
Resolution|--- |FIXED
Known to fail| |4.3.2
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
The code is accepted by GCC 7.0. Looks like the bug was fixed in r210284 (gcc
4.10.0):
r210284 | jason | 2014-05-09 14:16:11 -0400 (Fri, 09 May 2014) | 4 lines
DR 5
PR c++/60019
* call.c (build_user_type_conversion_1): The copy-init temporary
is cv-unqualified.