From: Mike Stump <mrs@apple.com>
To: naje <najeiv@ukr.net>
Cc: gcc@gcc.gnu.org
Subject: Re: compiler memory use optimization
Date: Thu, 18 Nov 2004 22:45:00 -0000 [thread overview]
Message-ID: <CA88A808-F327-4619-AF07-B88FCACB8040@apple.com> (raw)
In-Reply-To: <E1CUr6T-000KRL-CB@storage.ukr.net>
On Nov 18, 2004, at 10:33 AM, naje wrote:
> my program use C++ templates vary hard, so i've got much memory spent
> for
> compilation, and sometimes i've got "virtual memory exhaust" error.
> Is there any way to find out which part of my program is hard to
> compile to optimize it
Compile with -Q, and watch what is slow... Also, the { 20M -> 10M }
type numbers indicate how much memory was used by the compiler during
compilation of the corresponding function. The first is before GC, the
second is post GC.
Also, you might try a 4.0 snapshot with your code, so that you can see
the general trends, with some luck, it might be faster to compile and
require less memory.
Also, you can try things like -O2/-O0 and see if it is optimization
related, or not.
next prev parent reply other threads:[~2004-11-18 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 18:45 naje
2004-11-18 19:33 ` Giovanni Bajo
2004-11-18 22:30 ` Joe Buck
2004-11-18 22:45 ` Mike Stump [this message]
2004-11-21 6:49 Dan Kegel
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=CA88A808-F327-4619-AF07-B88FCACB8040@apple.com \
--to=mrs@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=najeiv@ukr.net \
/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).