public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pletzer at txcorp dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/39860] extremely long compile time Date: Thu, 23 Apr 2009 04:38:00 -0000 [thread overview] Message-ID: <20090423043837.15116.qmail@sourceware.org> (raw) In-Reply-To: <bug-39860-15934@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pletzer at txcorp dot com 2009-04-23 04:38 ------- Created an attachment (id=17681) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17681&action=view) source code reproducing problem I apologize but I cannot produce *.i files with -save-temps: [pletzer@localhost test]$ g++ -c -save-temps cxxps.cpp [pletzer@localhost test]$ ls ccps_base.h cxxps.cpp cxxps.o f77name.h ccps.h cxxps.h cxxps.tmp.localhost.localdomain.10206.s multiarray.h so I'm sending the source and headers as a bz2 compressed file. To reproduce the problem of very long compile time, type tar xvfj cxxps.bz2 g++ -c -O cxxps.cpp -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39860
next prev parent reply other threads:[~2009-04-23 4:38 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-23 4:23 [Bug c++/39860] New: " pletzer at txcorp dot com 2009-04-23 4:38 ` pletzer at txcorp dot com [this message] 2009-04-23 9:35 ` [Bug c++/39860] " rguenth 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=20090423043837.15116.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).