public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10060: ICE on huge file (300k lines)
Date: Fri, 09 May 2003 16:36:00 -0000	[thread overview]
Message-ID: <20030509163601.4343.qmail@sources.redhat.com> (raw)

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

From: Andrew Pinski <pinskia@physics.uc.edu>
To: "Giovanni Bajo" <giovannibajo@libero.it>
Cc: Andrew Pinski <pinskia@physics.uc.edu>, <andreas@florath.net>,
   <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>,
   <gcc-prs@gcc.gnu.org>
Subject: Re: c++/10060: ICE on huge file (300k lines)
Date: Fri, 9 May 2003 12:31:50 -0400

 That seems like a good idea, since copy_rtx_if_shared is in emit-rtl.c.
 
 
 Thanks,
 Andrew Pinski
 
 
 On Friday, May 9, 2003, at 09:10 US/Eastern, Giovanni Bajo wrote:
 
 > Andrew Pinski <pinskia@physics.uc.edu> wrote:
 >
 >>>  00281958 ggc_alloc (55, 0, 0, 550404, 0, 0)
 >>>  00129f98 copy_rtx_if_shared (0, 17527728, 0, 33a5c8, 2, 55) + 170
 >>>  00129f10 copy_rtx_if_shared (17527710, 17527b60, 0, 1, 33a5c8, 4c) +
 >>> e8
 >>>  00129f10 copy_rtx_if_shared (0, 17527f98, 0, 0, 33a5c8, 3) + e8
 >>>  00129f10 copy_rtx_if_shared (0, 175303d8, 0, 0, 33a5c8, 3) + e8
 >>>  00129f10 copy_rtx_if_shared (0, 17530810, 0, 0, 33a5c8, 3) + e8
 >
 >> This looks like a stack overflow, a temporary fix is to up the limit 
 >> on
 >> the stacksize.
 >> The real fix is to change copy_rtx_if_shared to be non-recursive.
 >
 > I'm not confident with internals of GCC, but I guess this bug should be
 > moved to the "middle-end" section. Do you agree, Andrew?
 >
 > Giovanni Bajo
 >
 >
 >
 


             reply	other threads:[~2003-05-09 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 16:36 Andrew Pinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 13:16 Giovanni Bajo
2003-05-09 13:06 Andrew Pinski
2003-05-09 13:06 andreas
2003-05-05 10:52 giovannibajo

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=20030509163601.4343.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).