public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/53666] New: -std=c++0x cause cc1plus to eat up RAM
@ 2012-06-14 3:21 slbyan at gmail dot com
2012-06-14 8:37 ` [Bug c++/53666] " rguenth at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: slbyan at gmail dot com @ 2012-06-14 3:21 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53666
Bug #: 53666
Summary: -std=c++0x cause cc1plus to eat up RAM
Classification: Unclassified
Product: gcc
Version: 4.6.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: slbyan@gmail.com
I have a line of code "static std::bitset<0X7FFFFFFFULL> bitSetPL;" in
main.cpp, a simple programme . It's wired to pass gcc with flag -std=c++0x,
even if no manipulation upon bitSetPL. It makes cc1plus to eat up memory :-(,
but it goes well if flag -std=c++0x removed.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-06-14 8:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-06-14 3:21 [Bug c++/53666] New: -std=c++0x cause cc1plus to eat up RAM slbyan at gmail dot com
2012-06-14 8:37 ` [Bug c++/53666] " rguenth at gcc dot gnu.org
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).