public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/100984] New: gimple-ssa-evrp.c: mismatched new and delete Date: Wed, 09 Jun 2021 06:38:29 +0000 [thread overview] Message-ID: <bug-100984-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100984 Bug ID: 100984 Summary: gimple-ssa-evrp.c: mismatched new and delete Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- I have just done a valgrind build of gcc trunk and it says: ==279305== Mismatched free() / delete / delete [] ==279305== at 0x48434DD: operator delete(void*) (vg_replace_malloc.c:802) ==279305== by 0x14B0691: ~pointer_equiv_analyzer (gimple-ssa-evrp.c:168) ==279305== Address 0x133d9a40 is 0 bytes inside a block of size 32 alloc'd ==279305== at 0x4842103: operator new[](unsigned long) (vg_replace_malloc.c:579) ==279305== by 0x14B0CB7: pointer_equiv_analyzer (gimple-ssa-evrp.c:163) Source code is pointer_equiv_analyzer::pointer_equiv_analyzer (gimple_ranger *r) { m_ranger = r; m_global_points = new tree[num_ssa_names] (); } pointer_equiv_analyzer::~pointer_equiv_analyzer () { delete m_global_points; } Suggest use [] on delete.
next reply other threads:[~2021-06-09 6:38 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-09 6:38 dcb314 at hotmail dot com [this message] 2021-06-09 6:41 ` [Bug c/100984] " dcb314 at hotmail dot com 2021-06-10 7:21 ` [Bug tree-optimization/100984] " aldyh at gcc dot gnu.org 2021-09-13 7:45 ` aldyh at gcc dot gnu.org 2021-09-13 7:51 ` 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-100984-4@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).