public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wouter dot vermaelen at pi dot be" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/29330] New: -O -ftree-loop-linear --> virtual memory exhausted Date: Tue, 03 Oct 2006 11:53:00 -0000 [thread overview] Message-ID: <bug-29330-8535@http.gcc.gnu.org/bugzilla/> (raw) > g++ -v Using built-in specs. Target: i486-linux-gnu Configured with: ../configure -v --enable-languages=c,c++ --prefix=/home/wouter/gcc/local --enable-shared --with-system-zlib --enable-nls --enable-threads=posix --without-included-gettext --disable-werror --enable-__cxa_atexit --enable-libstdcxx-allocator=mt --enable-clocale=gnu --enable-libstdcxx-debug i486-linux-gnu --enable-libmudflap --enable-checking=release Thread model: posix gcc version 4.2.0 20061003 (experimental) > g++ -O -ftree-loop-linear foo.cpp virtual memory exhausted: Cannot allocate memory > cat foo.cpp int buf[2][2][2][2]; void f() { for (int a = 0; a < 2; ++a) { for (int b = 0; b < 2; ++b) { for (int c = 0; c < 2; ++c) { for (int d = 0; d < 2; ++d) { buf[a][b][c][d] = 0; } } } } } -- Summary: -O -ftree-loop-linear --> virtual memory exhausted Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: wouter dot vermaelen at pi dot be http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29330
next reply other threads:[~2006-10-03 11:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-03 11:53 wouter dot vermaelen at pi dot be [this message] 2006-10-03 16:17 ` [Bug tree-optimization/29330] " pinskia at gcc dot gnu dot org 2006-10-03 16:21 ` pinskia at gcc dot gnu dot org 2006-10-03 18:19 ` pluto at agmk dot net 2006-10-05 4:48 ` [Bug tree-optimization/29330] [4.2 Regression] " pinskia at gcc dot gnu dot org 2006-10-06 4:37 ` robert dot wilhelm at gmx dot net 2006-10-06 12:49 ` jakub at gcc dot gnu dot org 2006-10-06 16:57 ` jakub at gcc dot gnu dot org 2006-10-06 17:17 ` jakub 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=bug-29330-8535@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).