public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/41043] [4.4 Regression] virtual memory exhausted: Cannot allocate memory
Date: Tue, 16 Feb 2010 16:12:00 -0000 [thread overview]
Message-ID: <20100216161208.27434.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41043-12313@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from rguenth at gcc dot gnu dot org 2010-02-16 16:12 -------
"Fixed" on trunk. Let's see if it causes any performance fallout.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail|4.4.1 4.5.0 |4.4.1
Known to work|4.3.4 |4.3.4 4.5.0
Summary|[4.4/4.5 Regression] virtual|[4.4 Regression] virtual
|memory exhausted: Cannot |memory exhausted: Cannot
|allocate memory |allocate memory
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41043
next prev parent reply other threads:[~2010-02-16 16:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 12:29 [Bug fortran/41043] New: [4.4/4.5 " dominiq at lps dot ens dot fr
2009-08-12 13:14 ` [Bug fortran/41043] " rguenth at gcc dot gnu dot org
2009-08-12 13:36 ` rguenth at gcc dot gnu dot org
2009-08-12 13:37 ` rguenth at gcc dot gnu dot org
2009-08-24 1:05 ` mmitchel at gcc dot gnu dot org
2009-10-15 12:58 ` [Bug middle-end/41043] " jakub at gcc dot gnu dot org
2010-01-02 21:02 ` fxcoudert at gcc dot gnu dot org
2010-02-16 10:27 ` rguenth at gcc dot gnu dot org
2010-02-16 13:00 ` rguenth at gcc dot gnu dot org
2010-02-16 13:18 ` rguenth at gcc dot gnu dot org
2010-02-16 13:22 ` dominiq at lps dot ens dot fr
2010-02-16 15:06 ` rguenth at gcc dot gnu dot org
2010-02-16 16:12 ` rguenth at gcc dot gnu dot org
2010-02-16 16:12 ` rguenth at gcc dot gnu dot org [this message]
2010-02-16 17:06 ` [Bug middle-end/41043] [4.4 " dominiq at lps dot ens dot fr
2010-02-17 9:40 ` rguenth at gcc dot gnu dot org
2010-02-21 12:49 ` dominiq at lps dot ens dot fr
2010-02-21 12:50 ` rguenther at suse dot de
2010-04-08 9:23 ` rguenth at gcc dot gnu dot org
2010-04-30 9:01 ` jakub at gcc dot gnu dot org
[not found] <bug-41043-4@http.gcc.gnu.org/bugzilla/>
2010-10-01 12:02 ` jakub at gcc dot gnu.org
2011-04-16 10:41 ` jakub at gcc dot gnu.org
2011-05-23 15:31 ` rguenth at gcc dot gnu.org
2011-12-08 12:32 ` dominiq at lps dot ens.fr
2012-02-22 12:37 ` xiaoyuanbo at yeah dot net
2012-03-06 22:12 ` dominiq at lps dot ens.fr
2012-03-06 22:18 ` jakub at gcc dot gnu.org
2012-03-13 16:10 ` jakub at gcc dot gnu.org
2014-09-11 10:58 ` 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=20100216161208.27434.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).