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++/94264] Array-to-pointer conversion not performed on array prvalues Date: Fri, 08 Dec 2023 18:34:51 +0000 [thread overview] Message-ID: <bug-94264-4-KqrGNlBJIB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94264-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94264 --- Comment #9 from GCC 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:5764825aed613f201a8bc47e5b239027a39691f0 commit r14-6342-g5764825aed613f201a8bc47e5b239027a39691f0 Author: Patrick Palka <ppalka@redhat.com> Date: Fri Dec 8 13:33:55 2023 -0500 c++: undiagnosed error_mark_node from cp_build_c_cast [PR112658] When cp_build_c_cast commits to an erroneous const_cast, we neglect to replay errors from build_const_cast_1 which can lead to us incorrectly accepting (and "miscompiling") the cast, or triggering the assert in finish_expr_stmt. This patch fixes this oversight. This was the original fix for the ICE in PR112658 before r14-5941-g305a2686c99bf9 made us accept the testcase there after all. I wasn't able to come up with an alternate testcase for which this fix has an effect anymore, but below is a reduced version of the PR112658 testcase (accepted ever since r14-5941) for good measure. PR c++/112658 PR c++/94264 gcc/cp/ChangeLog: * typeck.cc (cp_build_c_cast): If we're committed to a const_cast and the result is erroneous, call build_const_cast_1 a second time to issue errors. Use complain=tf_none instead of =false. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/initlist-array20.C: New test.
next prev parent reply other threads:[~2023-12-08 18:34 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-23 0:21 [Bug c++/94264] New: " ndkrempel at gmail dot com 2020-04-18 16:33 ` [Bug c++/94264] " mpolacek at gcc dot gnu.org 2021-08-10 3:43 ` pinskia at gcc dot gnu.org 2021-10-02 20:01 ` pinskia at gcc dot gnu.org 2023-10-08 7:31 ` fchelnokov at gmail dot com 2023-10-09 2:07 ` de34 at live dot cn 2023-10-09 2:19 ` pinskia at gcc dot gnu.org 2023-11-28 18:05 ` jason at gcc dot gnu.org 2023-11-28 21:29 ` cvs-commit at gcc dot gnu.org 2023-12-08 18:34 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-19 20:54 ` 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-94264-4-KqrGNlBJIB@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).