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 fortran/109010] Fortran frontend memory leaks building SPEC CPU 2017 Date: Fri, 03 Mar 2023 14:15:52 +0000 [thread overview] Message-ID: <bug-109010-4-iZgjJqQNGl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109010-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109010 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- I've tried to attach the full build log but it's too large even compressed. Instead I placed it at https://gcc.opensuse.org/CPU2017.449.log.xz but it might take a day or so for it to appear. Not all leaks might be easy to fix, but for example looking for __gmp_default_allocate reveals leaked GMP variables. I guess adding RAII class wrapper(s) might be a good cleanup opportunity here. Likewise gfc_expr_walker, used by frontend passes point to places that might leak memory not on the order of the number of source statements.
prev parent reply other threads:[~2023-03-03 14:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-03 14:06 [Bug fortran/109010] New: " rguenth at gcc dot gnu.org 2023-03-03 14:15 ` rguenth at gcc dot gnu.org [this message]
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-109010-4-iZgjJqQNGl@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).