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++/99080] Add !TYPE_P assert to type_dependent_expression_p Date: Mon, 30 May 2022 21:17:48 +0000 [thread overview] Message-ID: <bug-99080-4-yx7WVF8Fr9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99080-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99080 --- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:ff91735a5b861dd6eaf2c1e511f26a9255898e7d commit r13-860-gff91735a5b861dd6eaf2c1e511f26a9255898e7d Author: Marek Polacek <polacek@redhat.com> Date: Fri May 13 20:09:53 2022 -0400 c++: Add !TYPE_P assert to type_dependent_expression_p [PR99080] As discussed here: <https://gcc.gnu.org/pipermail/gcc-patches/2021-February/564629.html>, type_dependent_expression_p should not be called with a type argument. I promised I'd add an assert so here it is. One place needed adjusting. PR c++/99080 gcc/cp/ChangeLog: * pt.cc (type_dependent_expression_p): Assert !TYPE_P. * semantics.cc (finish_id_expression_1): Handle UNBOUND_CLASS_TEMPLATE specifically.
next prev parent reply other threads:[~2022-05-30 21:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-12 18:22 [Bug c++/99080] New: " mpolacek at gcc dot gnu.org 2021-02-12 18:22 ` [Bug c++/99080] " mpolacek at gcc dot gnu.org 2022-05-30 21:17 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-30 21:19 ` mpolacek 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-99080-4-yx7WVF8Fr9@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).