public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olh at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/21304] [4.0/4.1 regression] very long compile times with large cpp file from kdebindings Date: Mon, 02 May 2005 05:57:00 -0000 [thread overview] Message-ID: <20050502055738.8613.qmail@sourceware.org> (raw) In-Reply-To: <20050430195349.21304.olh@suse.de> ------- Additional Comments From olh at suse dot de 2005-05-02 05:57 ------- with CFLAGS=-O2 on ppc and --disable-checking: ==> 344.log <== 268.28user 0.82system 4:29.15elapsed 99%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+104891minor)pagefaults 0swaps ==> 401.log <== 9658.50user 6.57system 2:41:06elapsed 99%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (10major+197022minor)pagefaults 0swaps ==> 410.log <== 12455.82user 10.93system 3:27:49elapsed 99%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (5major+215621minor)pagefaults 0swaps on i686-linux, 3GHz xeon: GNU C++ version 3.4.4 20050430 (prerelease) (i686-pc-linux-gnu) 205.85user 1.89system 3:29.32elapsed 99%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (3major+95172minor)pagefaults 0swaps GNU C++ version 4.0.1 20050429 (prerelease) (i686-pc-linux-gnu) 6245.58user 4.21system 1:44:21elapsed 99%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (74major+309929minor)pagefaults 0swaps GNU C++ version 4.1.0 20050429 (experimental) (i686-pc-linux-gnu) 6409.50user 10.53system 1:51:28elapsed 95%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (4867major+351033minor)pagefaults 0swaps -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21304
next prev parent reply other threads:[~2005-05-02 5:57 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-30 19:53 [Bug c++/21304] New: " olh at suse dot de 2005-04-30 19:54 ` [Bug c++/21304] " olh at suse dot de 2005-04-30 19:58 ` [Bug middle-end/21304] " pinskia at gcc dot gnu dot org 2005-04-30 20:02 ` [Bug c++/21304] " pinskia at gcc dot gnu dot org 2005-04-30 20:19 ` pinskia at gcc dot gnu dot org 2005-04-30 20:25 ` pinskia at gcc dot gnu dot org 2005-04-30 23:04 ` dberlin at gcc dot gnu dot org 2005-04-30 23:37 ` pinskia at gcc dot gnu dot org 2005-05-01 4:11 ` olh at suse dot de 2005-05-01 8:10 ` olh at suse dot de 2005-05-02 3:34 ` [Bug tree-optimization/21304] [4.0/4.1 regression] " belyshev at depni dot sinp dot msu dot ru 2005-05-02 5:14 ` Andrew Pinski 2005-05-02 5:14 ` pinskia at physics dot uc dot edu 2005-05-02 5:57 ` olh at suse dot de [this message] 2005-07-23 23:55 ` pinskia at gcc dot gnu dot org 2005-07-24 0:14 ` pinskia at gcc dot gnu dot org 2005-09-19 1:08 ` pinskia at gcc dot gnu dot org 2005-09-27 15:59 ` mmitchel at gcc dot gnu dot org [not found] <bug-21304-1216@http.gcc.gnu.org/bugzilla/> 2005-10-12 16:12 ` pinskia at gcc dot gnu dot org 2005-10-13 3:10 ` pinskia at gcc dot gnu dot org 2005-10-14 3:01 ` cvs-commit at gcc dot gnu dot org
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=20050502055738.8613.qmail@sourceware.org \ --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: linkBe 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).