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 tree-optimization/109804] [11/12/13 Regression] internal compiler error in gimple-ssa-warn-access.cc Date: Thu, 22 Feb 2024 21:13:03 +0000 [thread overview] Message-ID: <bug-109804-4-lSQLq3UzoQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109804-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109804 --- Comment #14 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:a15427e75f2521ed5e467e3c5cb8446586bbdabb commit r13-8354-ga15427e75f2521ed5e467e3c5cb8446586bbdabb Author: Andrew Pinski <quic_apinski@quicinc.com> Date: Wed Feb 21 20:12:21 2024 -0800 warn-access: Fix handling of unnamed types [PR109804] This looks like an oversight of handling DEMANGLE_COMPONENT_UNNAMED_TYPE. DEMANGLE_COMPONENT_UNNAMED_TYPE only has the u.s_number.number set while the code expected newc.u.s_binary.left would be valid. So this treats DEMANGLE_COMPONENT_UNNAMED_TYPE like we treat function paramaters (DEMANGLE_COMPONENT_FUNCTION_PARAM) and template paramaters (DEMANGLE_COMPONENT_TEMPLATE_PARAM). Note the code in the demangler does this when it sets DEMANGLE_COMPONENT_UNNAMED_TYPE: ret->type = DEMANGLE_COMPONENT_UNNAMED_TYPE; ret->u.s_number.number = num; Committed as obvious after bootstrap/test on x86_64-linux-gnu PR tree-optimization/109804 gcc/ChangeLog: * gimple-ssa-warn-access.cc (new_delete_mismatch_p): Handle DEMANGLE_COMPONENT_UNNAMED_TYPE. gcc/testsuite/ChangeLog: * g++.dg/warn/Wmismatched-new-delete-8.C: New test. Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com> (cherry picked from commit 1076ffda6ce5e6d5fc9577deaf8233e549e5787a)
next prev parent reply other threads:[~2024-02-22 21:13 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-10 20:55 [Bug c++/109804] New: " christian.prochaska@genode-labs.com 2023-05-10 20:56 ` [Bug c++/109804] " christian.prochaska@genode-labs.com 2023-05-10 20:59 ` [Bug tree-optimization/109804] [11/12/13/14 Regression] " mpolacek at gcc dot gnu.org 2023-05-10 21:02 ` mpolacek at gcc dot gnu.org 2023-05-10 21:13 ` [Bug tree-optimization/109804] " pinskia at gcc dot gnu.org 2023-05-10 21:13 ` pinskia at gcc dot gnu.org 2023-05-10 21:14 ` pinskia at gcc dot gnu.org 2023-05-10 21:16 ` [Bug tree-optimization/109804] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-05-10 21:17 ` pinskia at gcc dot gnu.org 2023-05-10 21:18 ` pinskia at gcc dot gnu.org 2023-05-10 21:48 ` mpolacek at gcc dot gnu.org 2023-05-11 6:30 ` rguenth at gcc dot gnu.org 2023-05-29 10:08 ` jakub at gcc dot gnu.org 2024-02-21 7:23 ` pinskia at gcc dot gnu.org 2024-02-22 17:29 ` cvs-commit at gcc dot gnu.org 2024-02-22 17:30 ` [Bug tree-optimization/109804] [11/12/13 " pinskia at gcc dot gnu.org 2024-02-22 21:13 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-22 21:13 ` [Bug tree-optimization/109804] [11/12 " pinskia at gcc dot gnu.org 2024-05-08 17:11 ` cvs-commit at gcc dot gnu.org 2024-05-08 17:16 ` [Bug tree-optimization/109804] [11 " pinskia 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-109804-4-lSQLq3UzoQ@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).