public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/32598] New: [4.3 regression]: 27_io/basic_stringbuf/setbuf/wchar_t/4.cc needs more than 6GB memory to compile Date: Mon, 02 Jul 2007 22:36:00 -0000 [thread overview] Message-ID: <bug-32598-682@http.gcc.gnu.org/bugzilla/> (raw) Gcc 4.3 revision 126234 needs more than 6GB to compile 27_io/basic_stringbuf/setbuf/wchar_t/4.cc in libstdc++. It happens on Linux/ia32, Linux/ia64 and Linux/x86-64. Revision 126166 is OK. -- Summary: [4.3 regression]: 27_io/basic_stringbuf/setbuf/wchar_t/4.cc needs more than 6GB memory to compile Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl at lucon dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32598
next reply other threads:[~2007-07-02 22:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-02 22:36 hjl at lucon dot org [this message] 2007-07-02 23:37 ` [Bug c++/32598] " pcarlini at suse dot de 2007-07-02 23:38 ` pcarlini at suse dot de 2007-07-03 14:07 ` [Bug middle-end/32598] " rguenth at gcc dot gnu dot org 2007-07-03 14:15 ` [Bug middle-end/32598] [4.3 Regression]: " rguenth at gcc dot gnu dot org 2007-07-04 1:17 ` Joey dot ye at intel 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=bug-32598-682@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: 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).