From: Mark Mitchell <mark@codesourcery.com>
To: law@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Status Report (2004-09-13)
Date: Tue, 14 Sep 2004 05:58:00 -0000 [thread overview]
Message-ID: <41467AFA.3020200@codesourcery.com> (raw)
In-Reply-To: <1095135012.10968.268.camel@localhost.localdomain>
Jeffrey A Law wrote:
>On Mon, 2004-09-13 at 17:05, Mark Mitchell wrote:
>
>September 19
>
>
>* General compile-time performance improvements [Weinberg]
>
>Q. Presumably we can still also attack memory consumption
> issues as well. Right?
>
>The reason I ask is I have the first in what I expect will
>be a series of patches to start reducing memory consumption
>and bring more sense to our data structures.
>
>
Yes. We have a pretty good sense that reducing memory usage correlates
with reducing compile time, and, of course, people do not infinite RAM
anyhow, so this is a resource we should use prudently. The biggest
caveat is the one you have been raising recently: that touching pages
merely for the purpose of marking memory as free is by no means always a
win. But, if you can make data structures smaller in the first place,
and just allocate less along the way, that's going to help.
So, yes, this is OK -- but please do use your judgement about the
prudence of attempting major overhauls. The smaller the change (whether
in terms of lines of code or in terms of conceptual complexity) the
better, naturally.
--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com
next prev parent reply other threads:[~2004-09-14 5:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 0:30 Mark Mitchell
2004-09-14 1:14 ` Andrew Pinski
2004-09-14 1:28 ` Jan Hubicka
2004-09-14 5:02 ` Jeffrey A Law
2004-09-14 5:58 ` Mark Mitchell [this message]
2004-09-14 6:29 ` Jeffrey A Law
2004-09-14 15:54 ` Jan Hubicka
2004-09-14 17:07 ` Mark Mitchell
2004-09-14 6:28 ` Mark Mitchell
2004-09-15 21:25 ` Scott Robert Ladd
2004-09-16 21:58 ` Mark Mitchell
2004-09-16 15:58 ` GCC Status Report (2004-09-13) [--enable-mapped-location] Per Bothner
2004-09-16 18:45 ` Mark Mitchell
2004-09-16 18:56 ` Per Bothner
2004-09-16 19:02 ` Mark Mitchell
2004-09-16 19:03 ` Matt Austern
2004-09-16 19:31 ` Mark Mitchell
2004-09-16 22:50 ` Steven Bosscher
2004-09-16 19:28 ` Per Bothner
2004-09-16 19:46 ` Mark Mitchell
2004-09-14 4:48 GCC Status Report (2004-09-13) Wolfgang Bangerth
2004-09-18 11:02 Paolo Bonzini
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=41467AFA.3020200@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.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).