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 11:50:04 +0000 [thread overview] Message-ID: <bug-113476-4-5ZRuyHyy6j@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 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- In fact it occurs elsewhere as well: ==1854== 81,616 bytes in 2 blocks are possibly lost in loss record 1,363 of 1,373 ==1854== at 0x505A1DF: operator new[](unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==1854== by 0x1B8AB58: irange::maybe_resize(int) (value-range.h:645) ==1854== by 0x1B79873: irange::operator=(irange const&) (value-range.cc:948) ==1854== by 0x139779E: int_range<3u, true>::operator=(int_range<3u, true> const&) (value-range.h:1061) ==1854== by 0x2FAFBAE: phi_group::phi_group(phi_group const&) (gimple-range-phi.cc:84) ==1854== by 0x2FB0E7A: phi_analyzer::process_phi(gphi*) (gimple-range-phi.cc:460) ==1854== by 0x2FB0707: phi_analyzer::operator[](tree_node*) (gimple-range-phi.cc:314) ==1854== by 0x2F9E0E8: fold_using_range::range_of_phi(vrange&, gphi*, fur_source&) (gimple-range-fold.cc:949) ==1854== by 0x2F9C6AD: fold_using_range::fold_stmt(vrange&, gimple*, fur_source&, tree_node*) (gimple-range-fold.cc:604) ==1854== by 0x2F8D937: gimple_ranger::fold_range_internal(vrange&, gimple*, tree_node*) (gimple-range.cc:265) ==1854== by 0x2F8DC6D: gimple_ranger::range_of_stmt(vrange&, gimple*, tree_node*) (gimple-range.cc:326) ==1854== by 0x2F8E4D5: gimple_ranger::register_inferred_ranges(gimple*) (gimple-range.cc:486)
next prev parent reply other threads:[~2024-01-18 11:50 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 [this message] 2024-01-18 13:32 ` rguenth at gcc dot gnu.org 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-5ZRuyHyy6j@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).