From: Matt Austern <austern@apple.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Jan Hubicka <hubicka@ucw.cz>,
gcc-patches@gcc.gnu.org, stevenb@suse.de, rth@redhat.com
Subject: Re: Better memory statistics, take 2
Date: Thu, 02 Sep 2004 16:45:00 -0000 [thread overview]
Message-ID: <EEDA016B-FCFC-11D8-B904-000A95BCF344@apple.com> (raw)
In-Reply-To: <87eklk1vy6.fsf@codesourcery.com>
On Sep 2, 2004, at 9:23 AM, Zack Weinberg wrote:
> Jan Hubicka <hubicka@ucw.cz> writes:
>
>> Hi,
>> here is updated version of patch I sent while reducing memory for GCC
>> 3.4, it is quite usefull now again...
>>
>> Hi, this patch improves the per-line statistics by tracking down
>> each allocated entity to figure out whether it will be freed,
>> garbage collected or leaked. To rule out ggc_freed values is pretty
>> important as these are much cheaper,
> ...
>
> Please do timing tests before submitting any changes. In my
> experience ggc_free is *not* cheaper, it is by itself such an
> expensive operation that we don't actually gain anything over
> letting the garbage collector do its job.
What this does mean is that if we know a data structure will be
temporary, we shouldn't use ggc_free or ggc_anything.
--Matt
next prev parent reply other threads:[~2004-09-02 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 18:25 Make per-call statistics to take into account ggc_free Jan Hubicka
2004-03-19 8:14 ` Jan Hubicka
2004-09-02 16:12 ` Better memory statistics, take 2 Jan Hubicka
2004-09-02 16:27 ` Zack Weinberg
2004-09-02 16:45 ` Matt Austern [this message]
2004-09-02 16:47 ` Jan Hubicka
2004-09-02 17:15 ` Zack Weinberg
2004-09-02 17:23 ` Jan Hubicka
2004-09-02 17:28 ` Daniel Jacobowitz
2004-09-02 16:54 ` Jan Hubicka
2004-09-02 17:18 ` Richard Henderson
2021-08-17 9:17 ` Thomas Schwinge
2021-08-17 10:21 ` Richard Biener
2021-08-17 13:27 ` David Malcolm
2021-08-17 19:31 ` Thomas Schwinge
2021-08-18 7:02 ` Richard Biener
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=EEDA016B-FCFC-11D8-B904-000A95BCF344@apple.com \
--to=austern@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rth@redhat.com \
--cc=stevenb@suse.de \
--cc=zack@codesourcery.com \
/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).