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++/111357] [11/12/13/14 Regression] __integer_pack fails to work with values of dependent type convertible to integers in noexcept context
Date: Fri, 22 Sep 2023 14:36:36 +0000 [thread overview]
Message-ID: <bug-111357-4-50yrtqvm18@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111357-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111357
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
https://gcc.gnu.org/g:fd35d72a3dcd5ba14d81a1890236acd0145497e1
commit r14-4231-gfd35d72a3dcd5ba14d81a1890236acd0145497e1
Author: Jason Merrill <jason@redhat.com>
Date: Thu Sep 21 15:39:46 2023 +0100
c++ __integer_pack conversion again [PR111357]
As Jakub pointed out, the real problem here is that in a partial
substitution we're forgetting the conversion to the type of the non-type
template argument, because maybe_convert_nontype_argument doesn't do
anything with value-dependent arguments. I'm experimenting with changing
that, but in the meantime we can work around it here.
PR c++/111357
gcc/cp/ChangeLog:
* pt.cc (expand_integer_pack): Use IMPLICIT_CONV_EXPR.
next prev parent reply other threads:[~2023-09-22 14:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 2:16 [Bug libstdc++/111357] New: __integer_pack fails to work with values of dependent type convertible to integers frankhb1989 at gmail dot com
2023-09-10 3:33 ` [Bug c++/111357] " pinskia at gcc dot gnu.org
2023-09-10 3:52 ` [Bug c++/111357] __integer_pack fails to work with values of dependent type convertible to integers in noexcept context pinskia at gcc dot gnu.org
2023-09-10 3:56 ` [Bug c++/111357] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-09-11 8:54 ` redi at gcc dot gnu.org
2023-09-11 13:39 ` jason at gcc dot gnu.org
2023-09-11 13:43 ` jakub at gcc dot gnu.org
2023-09-12 17:27 ` cvs-commit at gcc dot gnu.org
2023-09-14 13:27 ` cvs-commit at gcc dot gnu.org
2023-09-14 13:39 ` cvs-commit at gcc dot gnu.org
2023-09-14 13:40 ` cvs-commit at gcc dot gnu.org
2023-09-14 13:42 ` cvs-commit at gcc dot gnu.org
2023-09-22 14:36 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-23 7:41 ` jakub at gcc dot gnu.org
2024-01-19 18:35 ` cvs-commit at gcc dot gnu.org
2024-01-19 19:29 ` jason 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-111357-4-50yrtqvm18@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: link
Be 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).