public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zadeck at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/34744] Memory leaks in compiler with empty program Date: Tue, 01 Jul 2008 14:06:00 -0000 [thread overview] Message-ID: <20080701140605.12453.qmail@sourceware.org> (raw) In-Reply-To: <bug-34744-10743@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from zadeck at gcc dot gnu dot org 2008-07-01 14:06 ------- Subject: Bug 34744 Author: zadeck Date: Tue Jul 1 14:05:13 2008 New Revision: 137319 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137319 Log: 2008-07-01 Kenneth Zadeck <zadeck@naturalbridge.com> PR rtl-optimization/34744 * df-scan.c (df_scan_free_ref_vec, df_scan_free_mws_vec): New macros. (df_scan_free_internal): Free data structures not allocated in storage pools. (df_mw_hardreg_chain_delete_eq_uses): Use df_scan_free_mws_vec. (df_refs_add_to_chains): Use df_scan_free_ref_vec and df_scan_free_mws_vec. * dse.c (dse_step6): Free offset_map_p and offset_map_n unconditionally. * ifcvt.c (cond_move_process_if_block): Free vectors on false return. Modified: branches/gcc-4_3-branch/gcc/ChangeLog branches/gcc-4_3-branch/gcc/df-scan.c branches/gcc-4_3-branch/gcc/dse.c branches/gcc-4_3-branch/gcc/ifcvt.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34744
prev parent reply other threads:[~2008-07-01 14:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-11 21:20 [Bug middle-end/34744] New: " jvdelisle at gcc dot gnu dot org 2008-01-12 14:03 ` [Bug middle-end/34744] " zadeck at naturalbridge dot com 2008-07-01 13:54 ` zadeck at naturalbridge dot com 2008-07-01 13:58 ` zadeck at gcc dot gnu dot org 2008-07-01 14:06 ` zadeck at gcc dot gnu dot 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=20080701140605.12453.qmail@sourceware.org \ --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).