From: Jeffrey A Law <law@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Status Report (2004-09-13)
Date: Tue, 14 Sep 2004 06:29:00 -0000 [thread overview]
Message-ID: <1095141173.10968.335.camel@localhost.localdomain> (raw)
In-Reply-To: <41467AFA.3020200@codesourcery.com>
On Mon, 2004-09-13 at 23:00, Mark Mitchell wrote:
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.
I expect I'll be looking at allocating fewer objects in the first
place rather than trying to allocate smaller objects.
> 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.
OK. Understood.
Thanks for the clarifications,
Jeff
next prev parent reply other threads:[~2004-09-14 5:53 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
2004-09-14 6:29 ` Jeffrey A Law [this message]
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=1095141173.10968.335.camel@localhost.localdomain \
--to=law@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@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).