This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
bootstrap/4952: genattrtab exhausts RAM while building tmp-attrtab.c
- From: jhrose at dial dot pipex dot com
- To: gcc-gnats at gcc dot gnu dot org
- Date: 27 Nov 2001 07:50:37 -0000
- Subject: bootstrap/4952: genattrtab exhausts RAM while building tmp-attrtab.c
- Reply-to: jhrose at dial dot pipex dot com
[Get raw message]
>Number: 4952
>Category: bootstrap
>Synopsis: genattrtab exhausts RAM while building tmp-attrtab.c
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: support
>Submitter-Id: net
>Arrival-Date: Mon Nov 26 23:56:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: julian rose (as reporters email)
>Release: gcc 3.0.2 (built using gcc 2.7.2, local host)
>Organization:
>Environment:
Host: Linux 2.0.18, gcc 2.7.2, libc (not glibc)
Config: i586-pc-linux-gnulibc1
HW: i586-75, 16MB RAM
>Description:
"genattrtab: virtual memory exhausted"
make [2]: [s-attrtab] error 23
make [1]: [stage1-build] error 2
error actually occurs in gensupport.c:xmalloc:902 (but incidental).
I couldn't get a stack out of gdb unfortunately to be precise, but
it seems to be a design problem rather than a bug.
>How-To-Repeat:
make bootstrap
>Fix:
Tritely, I should use another PC with more RAM :-)
Usefully, can genattrtab be made incremental rather than
storing all data in RAM prior to outputting (to tmp-attrtab.c)?
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="<none needed>"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="<none needed>"