public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/2160: signal 11 when compiling large generated program
@ 2002-04-25 17:45 rth
  0 siblings, 0 replies; 5+ messages in thread
From: rth @ 2002-04-25 17:45 UTC (permalink / raw)
  To: anton, gcc-bugs, gcc-prs, jsm28, nobody

Synopsis: signal 11 when compiling large generated program

State-Changed-From-To: analyzed->closed
State-Changed-By: rth
State-Changed-When: Thu Apr 25 17:45:27 2002
State-Changed-Why:
    This is the known computed-goto cfg manipulation problem.
    We've got nearly complete connectivity between a very large
    number of blocks, and we eat all that ram and time futzing
    with the edges between them.
    
    As such, I'm closing this as a duplicate of 4313, which
    identifies the problem more clearly.

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


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

* Re: c/2160: signal 11 when compiling large generated program
@ 2001-07-23  3:16 Anton Ertl
  0 siblings, 0 replies; 5+ messages in thread
From: Anton Ertl @ 2001-07-23  3:16 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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

From: Anton Ertl <anton@a0.complang.tuwien.ac.at>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/2160: signal 11 when compiling large generated program
Date: Mon, 23 Jul 2001 12:12:53 +0200 (MET DST)

 [This is a copy of a message already sent to
 anton@mips.complang.tuwien.ac.at, gcc-bugs@gcc.gnu.org,
 gcc-prs@gcc.gnu.org, jsm28@cam.ac.uk, nobody@gcc.gnu.org]
 
 jsm28@gcc.gnu.org wrote:
 >     Feedback at http://gcc.gnu.org/ml/gcc-bugs/2001-06/msg01531.html
 >     (not sent to gcc-gnats, so not filed with this PR).
 
 Should I do something else than replying to all recipients of your mail?
 
 >     Excess memory consumption is still a bug; changed from
 >     ice-on-legal-code to sw-bug.
 
 I finally managed to compile this file on an Alpha with 1GB with
 gcc-3.0 with
 
 gcc -mieee -c engine.i
 
 Top showed about 1550MB virtual memory consumption during most of the
 time.  Top showed that the CPU was mostly in system or idle mode, with
 only about 0.5% user time; took about 30 hours.  The compiler produced
 a file engine.o, so I assume the compilation went ok (unfortunately I
 was not smart enough to log the output and status).
 
 - anton
 
 


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

* Re: c/2160: signal 11 when compiling large generated program
@ 2001-07-23  3:06 Joseph S. Myers
  0 siblings, 0 replies; 5+ messages in thread
From: Joseph S. Myers @ 2001-07-23  3:06 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <anton@mips.complang.tuwien.ac.at>
Cc: <gcc-bugs@gcc.gnu.org>,  <gcc-gnats@gcc.gnu.org>
Subject: Re: c/2160: signal 11 when compiling large generated program
Date: Mon, 23 Jul 2001 11:05:32 +0100 (BST)

 On Mon, 23 Jul 2001, Anton Ertl wrote:
 
 > >     (not sent to gcc-gnats, so not filed with this PR).
 > 
 > Should I do something else than replying to all recipients of your mail?
 
 It needs to go to gcc-gnats@gcc.gnu.org to be filed with the PR.  GNATS
 status change messages used to include this address in the headers, but it
 seems they don't any more.  This is a bug in the bug tracking system
 configuration.
 
 > >     Excess memory consumption is still a bug; changed from
 > >     ice-on-legal-code to sw-bug.
 > 
 > I finally managed to compile this file on an Alpha with 1GB with
 > gcc-3.0 with
 > 
 > gcc -mieee -c engine.i
 > 
 > Top showed about 1550MB virtual memory consumption during most of the
 > time.  Top showed that the CPU was mostly in system or idle mode, with
 > only about 0.5% user time; took about 30 hours.  The compiler produced
 > a file engine.o, so I assume the compilation went ok (unfortunately I
 > was not smart enough to log the output and status).
 > 
 > - anton
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 


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

* Re: c/2160: signal 11 when compiling large generated program
@ 2001-07-20 14:17 jsm28
  0 siblings, 0 replies; 5+ messages in thread
From: jsm28 @ 2001-07-20 14:17 UTC (permalink / raw)
  To: anton, gcc-bugs, gcc-prs, jsm28, nobody

Synopsis: signal 11 when compiling large generated program

State-Changed-From-To: feedback->analyzed
State-Changed-By: jsm28
State-Changed-When: Fri Jul 20 14:17:36 2001
State-Changed-Why:
    Feedback at http://gcc.gnu.org/ml/gcc-bugs/2001-06/msg01531.html
    (not sent to gcc-gnats, so not filed with this PR).
    Excess memory consumption is still a bug; changed from
    ice-on-legal-code to sw-bug.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2160&database=gcc


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

* Re: c/2160: signal 11 when compiling large generated program
@ 2001-06-22  5:09 jsm28
  0 siblings, 0 replies; 5+ messages in thread
From: jsm28 @ 2001-06-22  5:09 UTC (permalink / raw)
  To: anton, gcc-bugs, gcc-prs, jsm28, nobody

Synopsis: signal 11 when compiling large generated program

State-Changed-From-To: open->feedback
State-Changed-By: jsm28
State-Changed-When: Fri Jun 22 05:09:19 2001
State-Changed-Why:
    Does this problem still occur with GCC 3.0?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2160&database=gcc


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

end of thread, other threads:[~2002-04-26  0:45 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-25 17:45 c/2160: signal 11 when compiling large generated program rth
  -- strict thread matches above, loose matches on Subject: below --
2001-07-23  3:16 Anton Ertl
2001-07-23  3:06 Joseph S. Myers
2001-07-20 14:17 jsm28
2001-06-22  5:09 jsm28

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