From: Jeffrey A Law <law@cygnus.com>
To: Per Bothner <bothner@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: Proposed new tree node for gcc
Date: Tue, 31 Mar 1998 00:46:00 -0000 [thread overview]
Message-ID: <14754.891330188@hurl.cygnus.com> (raw)
In-Reply-To: <199803280914.BAA22817@cygnus.com>
In message < 199803280914.BAA22817@cygnus.com >you write:
> One might say that this is excessive or premature space optimization.
> However, we know that many large compiles have problems due to large
> memory usage, so we might as well be economical, especially when
> there is no real reason not to be.
The vast majority of the memory usage problems have been in the
optimizers -- usually due to the need to allocate 1d and 2d arrays
based on register #s or INSN_UIDs.
I think the only time we've had any significant problems with the
tree space was when we used to have -fcombine-statics, which went
around copying nodes from temporary trees into permanent trees.
I'd kinda prefer to wait until we know that we're causing a memory
issues before making a hack like is being suggested.
jeff
next prev parent reply other threads:[~1998-03-31 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-24 14:49 Alexandre Petit-Bianco
1998-03-25 16:30 ` Richard Henderson
1998-03-27 15:18 ` Per Bothner
1998-03-26 21:49 ` Jeffrey A Law
1998-03-29 5:14 ` Per Bothner
1998-03-31 0:46 ` Jeffrey A Law [this message]
1998-03-31 0:20 ` Per Bothner
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=14754.891330188@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=bothner@cygnus.com \
--cc=egcs@cygnus.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).