public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
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 05:02:00 -0000	[thread overview]
Message-ID: <1095135012.10968.268.camel@localhost.localdomain> (raw)
In-Reply-To: <414627A4.4080109@codesourcery.com>

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.

The first patch converts our freelist of SSA_NAMEs to a bitmap;
ie, we no longer chain free nodes through the TREE_CHAIN field.
This allows us to attach information like global equivalences
and range information to the SSA_NAME rather than having that
information be stored in per-pass data structures.  This is
of interest as those per-pass data structures are allocated 
multiple times per function we compile and thus result in a
fair amount of garbage.

This first patch reduces memory in a very very tiny way (probably
due to fewer dangling pointers from SSA_NAMEs to statement nodes)
and is compile time neutral.

Anyway, I wanted to get a clarification on were we stand before
pushing those changes forward.

jeff

  parent reply	other threads:[~2004-09-14  4:10 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 [this message]
2004-09-14  5:58   ` Mark Mitchell
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=1095135012.10968.268.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).