public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/22392] Huge memory usage and infinite(?) loop with -fno-enforce-eh-specs
Date: Sun, 10 Jul 2005 18:22:00 -0000	[thread overview]
Message-ID: <20050710181229.10096.qmail@sourceware.org> (raw)
In-Reply-To: <20050710120034.22392.debian-gcc@lists.debian.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-10 18:12 -------
This is the scheduler messing up which is normal with big BBs.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c++                         |rtl-optimization
           Keywords|                            |compile-time-hog, memory-hog


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


  parent reply	other threads:[~2005-07-10 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-10 12:01 [Bug c++/22392] New: " debian-gcc at lists dot debian dot org
2005-07-10 12:22 ` [Bug c++/22392] " debian-gcc at lists dot debian dot org
2005-07-10 18:22 ` pinskia at gcc dot gnu dot org [this message]
2005-07-25  2:01 ` [Bug rtl-optimization/22392] " pinskia at gcc dot gnu dot org
     [not found] <bug-22392-5724@http.gcc.gnu.org/bugzilla/>
2007-04-28 13:21 ` falk at debian dot 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=20050710181229.10096.qmail@sourceware.org \
    --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).