public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/24153] memory leak
Date: Fri, 30 Sep 2005 23:04:00 -0000	[thread overview]
Message-ID: <20050930230402.10226.qmail@sourceware.org> (raw)
In-Reply-To: <20050930213317.24153.kazu@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-09-30 23:04 -------
Only 2 out of 5 are tree-opt problems.
==31716==    by 0x8589B01: discover_unique_type (ipa-type-escape.c:203)
And the DOM one.


The first one is related to splay_trees.  The second one I don't know a way to fix at all.

The rest rest were introduced by your self with:
2005-06-24  Kazu Hirata  <kazu@codesourcery.com>

        * cfglayout.c (block_locators_locs, line_locators_locs,
        line_locators_lines, file_locators_locs): Change the type to
        VEC(int,heap)*.
        (insn_locators_initialize, change_scope, insn_scope,
        locator_line, insn_line, locator_file): Use VEC instead of
        VARRAY.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|tree-optimization           |middle-end
           Keywords|                            |memory-hog


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24153


  parent reply	other threads:[~2005-09-30 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 21:33 [Bug tree-optimization/24153] New: " kazu at gcc dot gnu dot org
2005-09-30 21:34 ` [Bug tree-optimization/24153] " kazu at gcc dot gnu dot org
2005-09-30 23:04 ` pinskia at gcc dot gnu dot org [this message]
     [not found] <bug-24153-5009@http.gcc.gnu.org/bugzilla/>
2007-11-16 16:00 ` [Bug middle-end/24153] " manu at gcc dot gnu dot org
2008-01-26 12:11 ` rguenth at gcc dot gnu dot 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=20050930230402.10226.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: link
Be 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).