public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/58318] very slow compilation on x86_64-linux with -O3 and -g and checking enabled
Date: Thu, 19 Sep 2013 19:54:00 -0000 [thread overview]
Message-ID: <bug-58318-4-sfQ2zUn7GD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58318-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58318
--- Comment #3 from Zhendong Su <su at cs dot ucdavis.edu> ---
> A quick check with a non-bootstrapped cc1 but release checking makes the
> slowdown go away.
Richard, there is related testcase that I have just reported (58479). It
manifests also under release checking. Thanks.
prev parent reply other threads:[~2013-09-19 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 2:00 [Bug tree-optimization/58318] New: very slow compilation on x86_64-linux with -O3 and -g su at cs dot ucdavis.edu
2013-09-05 8:58 ` [Bug tree-optimization/58318] very slow compilation on x86_64-linux with -O3 and -g and checking enabled rguenth at gcc dot gnu.org
2013-09-05 15:23 ` su at cs dot ucdavis.edu
2013-09-19 19:54 ` su at cs dot ucdavis.edu [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=bug-58318-4-sfQ2zUn7GD@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).