public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martin at mpa-garching dot mpg dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/44483] New: [4.6 regression] gcc consumes all available memory when optimizing
Date: Wed, 09 Jun 2010 17:42:00 -0000 [thread overview]
Message-ID: <bug-44483-2736@http.gcc.gnu.org/bugzilla/> (raw)
When compiling the attached testcase, current trunk gcc uses all available
memory on my system (4GB) and then swaps until I interrupt the process. This
only happens with -O3; using -O2 works as expected.
gcc 4.5 comiles the file as expected with -O3.
/scratch/tmp/devel2/build.linux_gcc/libcfitsio>gcc -c -O3 -v checksum.i
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/afs/mpa/data/martin/ugcc/libexec/gcc/x86_64-unknown-linux-gnu/4.6.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /scratch/martin/gcc/configure --disable-bootstrap
--enable-gold --enable-plugins --prefix=/afs/mpa/data/martin/ugcc
--with-ppl=/afs/mpa/data/martin/numlibs64
--with-cloog=/afs/mpa/data/martin/numlibs64
--with-libelf=/afs/mpa/data/martin/numlibs64 --enable-languages=c++,fortran
--enable-target=all --enable-checking=release
Thread model: posix
gcc version 4.6.0 20100609 (experimental) [trunk revision 160476] (GCC)
COLLECT_GCC_OPTIONS='-c' '-O3' '-v' '-mtune=generic' '-march=x86-64'
/afs/mpa/data/martin/ugcc/libexec/gcc/x86_64-unknown-linux-gnu/4.6.0/cc1
-fpreprocessed checksum.i -quiet -dumpbase checksum.i -mtune=generic
-march=x86-64 -auxbase checksum -O3 -version -o /tmp/ccibJbLw.s
GNU C (GCC) version 4.6.0 20100609 (experimental) [trunk revision 160476]
(x86_64-unknown-linux-gnu)
compiled by GNU C version 4.4.2, GMP version 4.3.2, MPFR version 2.4.2,
MPC version 0.8.1
warning: GMP header version 4.3.2 differs from library version 4.3.1.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C (GCC) version 4.6.0 20100609 (experimental) [trunk revision 160476]
(x86_64-unknown-linux-gnu)
compiled by GNU C version 4.4.2, GMP version 4.3.2, MPFR version 2.4.2,
MPC version 0.8.1
warning: GMP header version 4.3.2 differs from library version 4.3.1.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: f4e23293da4cc17049a858a32373cf07
^C
/scratch/tmp/devel2/build.linux_gcc/libcfitsio>
--
Summary: [4.6 regression] gcc consumes all available memory when
optimizing
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: martin at mpa-garching dot mpg dot de
GCC build triplet: x86_64-unknown-linux-gnu
GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44483
next reply other threads:[~2010-06-09 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 17:42 martin at mpa-garching dot mpg dot de [this message]
2010-06-09 17:43 ` [Bug c/44483] " martin at mpa-garching dot mpg dot de
2010-06-09 19:11 ` [Bug tree-optimization/44483] " falk at debian dot org
2010-06-09 22:06 ` hjl dot tools at gmail dot com
2010-06-09 22:13 ` spop at gcc dot gnu dot org
2010-06-10 22:59 ` spop at gcc dot gnu dot org
2010-06-11 18:28 ` spop at gcc dot gnu dot org
2010-06-11 18:30 ` spop 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-44483-2736@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: link
Be 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).