public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: bootstrap/4952: genattrtab exhausts RAM while building tmp-attrtab.c
@ 2001-11-21  4:12 rth
  0 siblings, 0 replies; 3+ messages in thread
From: rth @ 2001-11-21  4:12 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR bootstrap/4952; it has been noted by GNATS.

From: rth@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  jhrose@dial.pipex.com, nobody@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/4952: genattrtab exhausts RAM while building tmp-attrtab.c
Date: 27 Nov 2001 08:21:33 -0000

 Synopsis: genattrtab exhausts RAM while building tmp-attrtab.c
 
 State-Changed-From-To: open->closed
 State-Changed-By: rth
 State-Changed-When: Tue Nov 27 00:21:33 2001
 State-Changed-Why:
     Increase swap space.  For the x86 target, genattrtab requires
     about 41MB of virtual memory.  This is down from ~120MB in some
     gcc3 pre-releases, so it is unlikely there is much more space
     that could be saved.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4952&database=gcc


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: bootstrap/4952: genattrtab exhausts RAM while building tmp-attrtab.c
@ 2001-11-21  4:10 rth
  0 siblings, 0 replies; 3+ messages in thread
From: rth @ 2001-11-21  4:10 UTC (permalink / raw)
  To: gcc-bugs, gcc-gnats, gcc-prs, jhrose, nobody

Synopsis: genattrtab exhausts RAM while building tmp-attrtab.c

State-Changed-From-To: open->closed
State-Changed-By: rth
State-Changed-When: Tue Nov 27 00:21:33 2001
State-Changed-Why:
    Increase swap space.  For the x86 target, genattrtab requires
    about 41MB of virtual memory.  This is down from ~120MB in some
    gcc3 pre-releases, so it is unlikely there is much more space
    that could be saved.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4952&database=gcc


^ permalink raw reply	[flat|nested] 3+ messages in thread

* bootstrap/4952: genattrtab exhausts RAM while building tmp-attrtab.c
@ 2001-11-21  4:06 jhrose
  0 siblings, 0 replies; 3+ messages in thread
From: jhrose @ 2001-11-21  4:06 UTC (permalink / raw)
  To: gcc-gnats


>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>"


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-11-27  8:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-11-21  4:12 bootstrap/4952: genattrtab exhausts RAM while building tmp-attrtab.c rth
  -- strict thread matches above, loose matches on Subject: below --
2001-11-21  4:10 rth
2001-11-21  4:06 jhrose

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).