From: Charles <qe@dabney.com>
To: John Carter <john.carter@tait.co.nz>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re[2]: Extremely long compile times
Date: Mon, 21 Oct 2002 13:40:00 -0000 [thread overview]
Message-ID: <20021021134000.qscY7dYgFqwoJw048vcNScjKKIH-lmprAweVbeopy4k@z> (raw)
In-Reply-To: <Pine.LNX.4.44.0210210907590.21282-100000@parore>
Thanks, much, John.
Moving the variables outside of "main" fixed the problem.
Thanks again.
Charles
On Mon, 21 Oct 2002 09:13:01 +1300 (NZDT) John Carter <john.carter@tait.co.nz> wrote:
> On Fri, 18 Oct 2002, Charles wrote:
>
> > I've tried this with both gcc 3.1.1 and gcc 3.2. This particular
> program
> > takes over 2 hours to compile.
>
...
> It could be that gcc is doing a linear search somewhere under the
> expectation that there aren't a huge number of local variables. Can you
> try break it up into smaller compilation units?
prev parent reply other threads:[~2002-10-21 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200210181219.g9ICJ9Y01412@gatekeeper.tait.co.nz>
2002-10-20 13:13 ` John Carter
2002-10-21 13:40 ` Re[2]: " Charles
2002-10-21 13:40 ` Charles [this message]
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=20021021134000.qscY7dYgFqwoJw048vcNScjKKIH-lmprAweVbeopy4k@z \
--to=qe@dabney.com \
--cc=gcc-help@gcc.gnu.org \
--cc=john.carter@tait.co.nz \
/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).