public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/43058] [4.5 Regression] var-tracking uses up all virtual memory
Date: Tue, 23 Mar 2010 06:49:00 -0000 [thread overview]
Message-ID: <20100323064852.27745.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43058-10053@http.gcc.gnu.org/bugzilla/>
------- Comment #17 from jakub at gcc dot gnu dot org 2010-03-23 06:48 -------
But clearly it is not var-tracking that eats all the memory, instead it is the
scheduler, and it happens also with -g0, and doesn't happen with
-fno-schedule-insns -fno-schedule-insns2. So, please open a separate bugreport
about it, reopening this one for unrelated reasons will just lead to confusion.
I guess I could add { target { ! "ia64-*-*" } } as a quick workaround.
--
jakub at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43058
prev parent reply other threads:[~2010-03-23 6:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 19:04 [Bug rtl-optimization/43058] New: " rguenth at gcc dot gnu dot org
2010-02-13 19:06 ` [Bug rtl-optimization/43058] " rguenth at gcc dot gnu dot org
2010-02-13 19:13 ` rguenth at gcc dot gnu dot org
2010-02-13 19:25 ` rguenth at gcc dot gnu dot org
2010-02-13 19:38 ` rguenth at gcc dot gnu dot org
2010-02-13 19:57 ` rguenth at gcc dot gnu dot org
2010-02-15 16:57 ` rguenth at gcc dot gnu dot org
2010-02-17 16:57 ` mmitchel at gcc dot gnu dot org
2010-02-19 11:55 ` rguenth at gcc dot gnu dot org
2010-02-24 18:25 ` jakub at gcc dot gnu dot org
2010-03-05 15:19 ` jakub at gcc dot gnu dot org
2010-03-12 12:06 ` rguenth at gcc dot gnu dot org
2010-03-17 10:58 ` jakub at gcc dot gnu dot org
2010-03-17 15:05 ` jakub at gcc dot gnu dot org
2010-03-18 20:15 ` jakub at gcc dot gnu dot org
2010-03-18 20:31 ` jakub at gcc dot gnu dot org
2010-03-23 0:58 ` wilson at gcc dot gnu dot org
2010-03-23 6:49 ` jakub at gcc dot gnu dot org [this message]
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=20100323064852.27745.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).