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++/110468] [12/13/14 regression] Internal compiler error in nothrow_spec_p Date: Thu, 29 Jun 2023 20:10:53 +0000 [thread overview] Message-ID: <bug-110468-4-Wu9O1wRvgu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110468-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110468 --- Comment #13 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:9479da4515f7d019b4ef282d0e21536431c44f71 commit r14-2199-g9479da4515f7d019b4ef282d0e21536431c44f71 Author: Patrick Palka <ppalka@redhat.com> Date: Thu Jun 29 16:10:18 2023 -0400 c++: NSDMI instantiation during overload resolution [PR110468] Here we find ourselves instantiating the NSDMI for A<1>::m when computing argument conversions during overload resolution, and thus tf_conv is set. The flag causes mark_used for the constructor used in the NSDMI to exit early and not instantiate its noexcept-spec, which eventually leads to an ICE from nothrow_spec_p. This patch fixes this by clearing any special tsubst flags during instantiation of an NSDMI, since the result should be independent of the context that requires the instantiation. PR c++/110468 gcc/cp/ChangeLog: * init.cc (maybe_instantiate_nsdmi_init): Mask out all tsubst flags except for tf_warning_or_error. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/noexcept79.C: New test.
next prev parent reply other threads:[~2023-06-29 20:10 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-28 19:40 [Bug c++/110468] New: internal compiler error in nothrow_spec_p (g++ > 11) gococobu at 7art dot org 2023-06-28 19:53 ` [Bug c++/110468] " mpolacek at gcc dot gnu.org 2023-06-28 20:13 ` gococobu at 7art dot org 2023-06-28 20:26 ` pinskia at gcc dot gnu.org 2023-06-28 20:34 ` gococobu at 7art dot org 2023-06-28 20:38 ` gococobu at 7art dot org 2023-06-28 20:38 ` pinskia at gcc dot gnu.org 2023-06-28 20:38 ` pinskia at gcc dot gnu.org 2023-06-28 21:08 ` gococobu at 7art dot org 2023-06-28 21:09 ` pinskia at gcc dot gnu.org 2023-06-29 1:09 ` [Bug c++/110468] [12/13/14 regression] Internal compiler error in nothrow_spec_p pinskia at gcc dot gnu.org 2023-06-29 1:16 ` pinskia at gcc dot gnu.org 2023-06-29 1:18 ` gococobu at 7art dot org 2023-06-29 12:12 ` ppalka at gcc dot gnu.org 2023-06-29 20:10 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-01 1:28 ` cvs-commit at gcc dot gnu.org 2023-07-12 19:28 ` cvs-commit at gcc dot gnu.org 2023-07-12 19:29 ` 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-110468-4-Wu9O1wRvgu@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).