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 rust/111899] [14 regression] GCC fails to bootstrap with 'rust-tree.cc:131:10: error: ‘NON_DEPENDENT_EXPR’ was not declared in this scope' Date: Fri, 20 Oct 2023 17:36:56 +0000 [thread overview] Message-ID: <bug-111899-4-8OCTEPE7Ys@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111899-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111899 --- Comment #4 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:5ac53c025e08b4c464b02cfc595e422813023c81 commit r14-4800-g5ac53c025e08b4c464b02cfc595e422813023c81 Author: Patrick Palka <ppalka@redhat.com> Date: Fri Oct 20 13:36:11 2023 -0400 rust: build failure after NON_DEPENDENT_EXPR removal [PR111899] This patch removes stray NON_DEPENDENT_EXPR checks following the removal of this tree code from the C++ FE. (Since this restores the build I supppose it means the Rust FE never creates NON_DEPENDENT_EXPR trees in the first place, so no further analysis is needed.) PR rust/111899 gcc/rust/ChangeLog: * backend/rust-constexpr.cc (potential_constant_expression_1): Remove NON_DEPENDENT_EXPR handling. * backend/rust-tree.cc (mark_exp_read): Likewise. (mark_use): Likewise. (lvalue_kind): Likewise.
next prev parent reply other threads:[~2023-10-20 17:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-20 16:40 [Bug c++/111899] New: [14 regression] GCC fails to bootstrap with 'ust-tree.cc:131:10: " sjames at gcc dot gnu.org 2023-10-20 16:42 ` [Bug rust/111899] [14 regression] GCC fails to bootstrap with 'rust-tree.cc:131:10: " pinskia at gcc dot gnu.org 2023-10-20 16:43 ` mpolacek at gcc dot gnu.org 2023-10-20 16:44 ` pinskia at gcc dot gnu.org 2023-10-20 17:02 ` ppalka at gcc dot gnu.org 2023-10-20 17:11 ` ppalka at gcc dot gnu.org 2023-10-20 17:36 ` cvs-commit at gcc dot gnu.org [this message] 2023-10-20 18:14 ` 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-111899-4-8OCTEPE7Ys@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).