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/115208] [15 Regression] Memory consumption get extremely high after r15-807-gfae5e6a4dfcf92 Date: Sun, 26 May 2024 01:46:17 +0000 [thread overview] Message-ID: <bug-115208-4-cNt8q8NGbA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115208-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115208 --- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>: https://gcc.gnu.org/g:f9810728cf42ea7c3d84198aa582e53cfb2302d1 commit r15-833-gf9810728cf42ea7c3d84198aa582e53cfb2302d1 Author: Andrew MacLeod <amacleod@redhat.com> Date: Sat May 25 12:28:52 2024 -0400 Delete gori_map during destruction of GORI. Forgot to free the gori_mpa object when a gori object is freed. PR tree-optimization/115208 * value-query.cc (range_query::create_gori): Confirm gori_map is NULL. (range_query::destroy_gori): Free gori_map if one was allocated.
next prev parent reply other threads:[~2024-05-26 1:46 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-24 6:35 [Bug middle-end/115208] New: [15 Regression] Memory consumption get extremely high after r15-809 haochen.jiang at intel dot com 2024-05-24 6:39 ` [Bug middle-end/115208] " haochen.jiang at intel dot com 2024-05-24 6:41 ` [Bug tree-optimization/115208] " pinskia at gcc dot gnu.org 2024-05-24 7:39 ` rguenth at gcc dot gnu.org 2024-05-24 13:22 ` pinskia at gcc dot gnu.org 2024-05-24 14:08 ` ro at gcc dot gnu.org 2024-05-25 2:16 ` [Bug tree-optimization/115208] [15 Regression] Memory consumption get extremely high after r15-807-gfae5e6a4dfcf92 sjames at gcc dot gnu.org 2024-05-25 15:08 ` schwab@linux-m68k.org 2024-05-25 16:38 ` amacleod at redhat dot com 2024-05-25 19:46 ` slyfox at gcc dot gnu.org 2024-05-26 1:46 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-26 9:12 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-26 12:43 ` haochen.jiang at intel dot com
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-115208-4-cNt8q8NGbA@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).