public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rspencer at x10sys dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/27140] Compiling LLVM now takes nearly 5x as long with 4.1 as it did with 4.0 Date: Thu, 13 Apr 2006 07:48:00 -0000 [thread overview] Message-ID: <20060413074809.10269.qmail@sourceware.org> (raw) In-Reply-To: <bug-27140-10546@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from rspencer at x10sys dot com 2006-04-13 07:48 ------- Created an attachment (id=11253) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11253&action=view) source code and -ftime-report output for both 4.0.2 and 4.1.0 This tarball contains 2MB of pre-compiled source code (slow.cpp) as well as two output files (slow.out=4.1.0 and fast.out=4.0.2). These contain the command lines used, the "gcc -v" output and the "gcc -ftime-report" output. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27140
next prev parent reply other threads:[~2006-04-13 7:48 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-04-13 7:44 [Bug c++/27140] New: " rspencer at x10sys dot com 2006-04-13 7:48 ` rspencer at x10sys dot com [this message] 2006-04-13 16:30 ` [Bug tree-optimization/27140] " pinskia at gcc dot gnu dot org 2006-04-13 16:31 ` sabre at nondot dot org 2006-04-13 17:26 ` rspencer at x10sys dot com 2006-04-13 20:14 ` rspencer at x10sys dot com 2006-04-13 20:30 ` rspencer at x10sys dot com 2006-04-13 22:40 ` Daniel Berlin 2006-04-13 22:40 ` dberlin at dberlin dot org 2006-04-17 10:16 ` rguenth at gcc dot gnu dot org 2006-04-21 23:12 ` rspencer at x10sys dot com 2006-10-17 22:42 ` rspencer at x10sys dot com 2006-10-17 22:44 ` Andrew Pinski 2006-10-17 22:44 ` pinskia at physics dot uc dot edu 2008-01-26 23:00 ` rguenth at gcc dot gnu dot org 2008-09-03 2:13 ` pinskia at gcc dot gnu dot org 2009-08-14 16:27 ` jessieluv22 at gmail dot com
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=20060413074809.10269.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).