public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55135] Segfault of gcc on a big file
Date: Thu, 28 Feb 2013 23:59:00 -0000	[thread overview]
Message-ID: <bug-55135-4-9UWuwDtmaR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55135-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55135

--- Comment #10 from Steven Bosscher <steven at gcc dot gnu.org> 2013-02-28 23:58:38 UTC ---
Created attachment 29557
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29557
Collected hacks to make the test case compile in reasonable time with -O0

Patch does 2 things:

- Queue up to-be-removed EH regions, instead of removing them one-by-one.
  Removing them one at a time results in walking the list of EH regions
  repeatedly, thus taking O(# of EH regions ** 2) time.

- Rewrite init_subregs_of_mode and subroutines to first collect the
  invalid mode change subregs in sbitmaps, and then converting the final
  sbitmap to a bitmap. This trades memory for time: the bitmap lookups are
  also potentially O(# of registers ** 2) and this test case has more than
  one million registers, many of them with invalid mode changes (to be fixed
  up by IRA/LRA).

Peak memory at -O0 is <4GB. Compile time on a "Quad-Core AMD Opteron(tm)
Processor 8354" at 2200MHz is 240s, half of it still taken up by IRA+LRA.

At -O1 the einline pass is consuming almost all compile time again.
-> Honza: Can we please have a proper permanent fix for this recurring
problem? What's there now just Does Not Work!


  parent reply	other threads:[~2013-02-28 23:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 10:18 [Bug c++/55135] New: " benoit.barbot at gmail dot com
2012-10-30 10:28 ` [Bug c++/55135] " benoit.barbot at gmail dot com
2012-10-30 10:40 ` mpolacek at gcc dot gnu.org
2012-10-30 11:48 ` paolo.carlini at oracle dot com
2012-10-30 13:29 ` benoit.barbot at gmail dot com
2012-10-30 14:04 ` markus at trippelsdorf dot de
2012-10-31 16:32 ` benoit.barbot at gmail dot com
2012-10-31 16:46 ` markus at trippelsdorf dot de
2012-11-07 15:11 ` paolo.carlini at oracle dot com
2013-02-27 16:21 ` paolo.carlini at oracle dot com
2013-02-28 22:49 ` steven at gcc dot gnu.org
2013-02-28 23:59 ` steven at gcc dot gnu.org [this message]
2013-03-01  0:02 ` [Bug c++/55135] [4.8 Regression] " steven at gcc dot gnu.org
2013-03-01  7:51 ` steven at gcc dot gnu.org
2013-03-01  7:52 ` steven at gcc dot gnu.org
2013-03-01  9:36 ` paolo.carlini at oracle dot com
2013-03-01 10:37 ` rguenth at gcc dot gnu.org
2013-03-01 10:44 ` rguenth at gcc dot gnu.org
2013-03-01 14:35 ` steven at gcc dot gnu.org
2013-03-01 16:14 ` hubicka at ucw dot cz
2013-03-01 16:20 ` hubicka at ucw dot cz
2013-03-01 19:13 ` steven at gcc dot gnu.org
2013-03-01 21:05 ` steven at gcc dot gnu.org
2013-03-05 14:46 ` steven at gcc dot gnu.org
2013-03-05 16:41 ` steven at gcc dot gnu.org
2013-03-06 10:47 ` [Bug c++/55135] " rguenth at gcc dot gnu.org
2013-03-06 12:09 ` steven at gcc dot gnu.org
2013-03-06 12:10 ` steven at gcc dot gnu.org
2013-03-06 12:14 ` rguenther at suse dot de
2013-03-06 12:16 ` rguenth at gcc dot gnu.org
2013-03-06 12:18 ` steven at gcc dot gnu.org
2013-03-06 12:23 ` rguenther at suse dot de
2020-09-28  7:24 ` [Bug middle-end/55135] " rguenth at gcc dot gnu.org
2020-09-28  8:16 ` hubicka at ucw dot cz
2024-02-19 12:35 ` rguenth at gcc dot gnu.org

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=bug-55135-4-9UWuwDtmaR@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).