From: Charles <qe@dabney.com>
To: gcc-help@gcc.gnu.org
Subject: Extremely long compile times
Date: Fri, 18 Oct 2002 05:18:00 -0000 [thread overview]
Message-ID: <20021018051800.i98hfEOwP1U3KkVm6pznon8Rtvx_Zbmc7zy5Ty_ujI0@z> (raw)
I've tried this with both gcc 3.1.1 and gcc 3.2. This particular program
takes over 2 hours to compile. According to -time, 100% of the time is
spent in "cfg cleanup". The program is generated by a language converter
we are working on and contains only a "main" function with a very large
number of local variables and initializing of arrays one element at a time.
Does anyone know what could be causing this and/or what we could look for
to correct it?
TIA,
Charles
next reply other threads:[~2002-10-18 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 5:18 Charles [this message]
2002-10-18 5:18 Charles
[not found] <200210181219.g9ICJ9Y01412@gatekeeper.tait.co.nz>
2002-10-20 13:13 ` John Carter
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=20021018051800.i98hfEOwP1U3KkVm6pznon8Rtvx_Zbmc7zy5Ty_ujI0@z \
--to=qe@dabney.com \
--cc=gcc-help@gcc.gnu.org \
/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).