public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/32266] New: Excessive memory usage (805M!)
@ 2007-06-08 23:36 jsberg04+computing dot bugs dot gcc at ftml dot net
2007-06-08 23:38 ` [Bug middle-end/32266] " pinskia at gcc dot gnu dot org
2007-06-08 23:39 ` jsberg04+computing dot bugs dot gcc at ftml dot net
0 siblings, 2 replies; 3+ messages in thread
From: jsberg04+computing dot bugs dot gcc at ftml dot net @ 2007-06-08 23:36 UTC (permalink / raw)
To: gcc-bugs
I will attach the example in a subsequent comment. If I execute:
gcc -O1 -c xf86ScanPci.c
it sucks up 805M of virtual memory. No optimization, no problem.
gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.2.0/configure --prefix=/opt/gcc-4.2.0
--enable-threads --with-system-zlib --with-gmp=/opt/gmp-4.2.1
--with-mpfr=/opt/mpfr-2.2.1 --enable-__cxa_atexit
Thread model: posix
gcc version 4.2.0
--
Summary: Excessive memory usage (805M!)
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jsberg04+computing dot bugs dot gcc at ftml dot net
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32266
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-06-08 23:39 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-06-08 23:36 [Bug c/32266] New: Excessive memory usage (805M!) jsberg04+computing dot bugs dot gcc at ftml dot net
2007-06-08 23:38 ` [Bug middle-end/32266] " pinskia at gcc dot gnu dot org
2007-06-08 23:39 ` jsberg04+computing dot bugs dot gcc at ftml dot net
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).