public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113476] [14 Regression] irange::maybe_resize leaks memory via IPA VRP Date: Thu, 18 Jan 2024 13:32:29 +0000 [thread overview] Message-ID: <bug-113476-4-ZryVc3fqnf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113476-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113476 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aldyh at gcc dot gnu.org, | |jamborm at gcc dot gnu.org --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Ah, so it's we have class ipcp_vr_lattice { public: Value_Range m_vr; inline bool bottom_p () const; inline bool top_p () const; inline bool set_to_bottom (); bool meet_with (const vrange &p_vr); bool meet_with (const ipcp_vr_lattice &other); void init (tree type); void print (FILE * f); private: bool meet_with_1 (const vrange &other_vr); }; so no explicit DTOR and if we destroy the object then Value_Range doesn't have a CTOR. I also don't see we destroy ipcp_param_lattices? Of course irange doesn't have a DTOR in the first place ... Martin? Andrew?
next prev parent reply other threads:[~2024-01-18 13:32 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 11:43 [Bug tree-optimization/113476] New: " rguenth at gcc dot gnu.org 2024-01-18 11:43 ` [Bug tree-optimization/113476] " rguenth at gcc dot gnu.org 2024-01-18 11:48 ` rguenth at gcc dot gnu.org 2024-01-18 11:50 ` rguenth at gcc dot gnu.org 2024-01-18 13:32 ` rguenth at gcc dot gnu.org [this message] 2024-01-22 17:48 ` jamborm at gcc dot gnu.org 2024-01-23 6:58 ` rguenth at gcc dot gnu.org 2024-02-19 15:05 ` jamborm at gcc dot gnu.org 2024-02-21 9:15 ` aldyh at gcc dot gnu.org 2024-02-21 9:17 ` aldyh at gcc dot gnu.org 2024-02-21 9:18 ` aldyh at gcc dot gnu.org 2024-02-21 9:19 ` aldyh at gcc dot gnu.org 2024-02-21 11:22 ` aldyh at gcc dot gnu.org 2024-02-21 11:25 ` jakub at gcc dot gnu.org 2024-02-21 11:55 ` aldyh at gcc dot gnu.org 2024-02-21 12:10 ` jakub at gcc dot gnu.org 2024-02-21 14:43 ` [Bug ipa/113476] " cvs-commit at gcc dot gnu.org 2024-02-21 14:44 ` jamborm at gcc dot gnu.org 2024-02-22 7:38 ` rguenther at suse dot de 2024-02-22 16:07 ` aldyh 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-113476-4-ZryVc3fqnf@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).