From: Daniel Berlin <dberlin@dberlin.org>
To: Steven Bosscher <s.bosscher@student.tudelft.nl>
Cc: Diego Novillo <dnovillo@redhat.com>,
Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: tree-ssa branch: Call for preliminary testing
Date: Mon, 12 May 2003 13:59:00 -0000 [thread overview]
Message-ID: <E4499C0C-8481-11D7-87A1-000A95A34564@dberlin.org> (raw)
In-Reply-To: <1052744480.2035.40.camel@steven>
On Monday, May 12, 2003, at 09:01 AM, Steven Bosscher wrote:
> Op ma 12-05-2003, om 14:43 schreef Diego Novillo:
>> On Sun, 2003-05-11 at 13:11, Richard Guenther wrote:
>>> cc1plus: out of memory allocating 564784160 bytes after a total of
>>> 28152172 bytes
>>> Command exited with non-zero status 1
>
> FWIW, this is not the first report of such a message showing up. I've
> seen it at least twice for something involving the preprocessor.
> I really can't think of _any_ situation where we would want to allocate
> 564MB in one big chunk, so this really is a bug somewhere.
Apparently you've never had the joy of working with some form of
interference graph.
:)
Andrew, if this relationship is symmetric (ie a interferes with b
implies b interferes with a), you can halve the size and represent it
as a triangular bitmatrix like we do in new-regalloc.
grep for igraph and igraph_index.
>
> Gr.
> Steven
>
>
next prev parent reply other threads:[~2003-05-12 13:59 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 17:11 Richard Guenther
2003-05-12 12:43 ` Diego Novillo
2003-05-12 12:58 ` Steven Bosscher
2003-05-12 13:08 ` Andrew MacLeod
2003-05-12 13:16 ` Diego Novillo
2003-05-12 13:22 ` Andrew MacLeod
2003-05-12 13:49 ` Richard Guenther
2003-05-12 14:05 ` Daniel Berlin
2003-05-12 14:16 ` Andrew MacLeod
2003-05-12 14:17 ` Diego Novillo
2003-06-12 15:36 ` Diego Novillo
2003-05-12 13:02 ` Steven Bosscher
2003-05-12 13:09 ` Diego Novillo
2003-05-12 13:59 ` Daniel Berlin [this message]
2003-05-12 14:12 ` Andrew MacLeod
2003-05-12 13:02 ` Richard Guenther
2003-06-12 16:09 ` Diego Novillo
2003-06-12 21:10 ` Richard Guenther
2003-06-12 21:29 ` Diego Novillo
2003-06-13 9:58 ` Richard Guenther
2003-06-13 11:38 ` Diego Novillo
2003-06-14 11:41 ` Richard Guenther
2003-06-13 20:15 ` Andrew MacLeod
2003-06-14 20:06 ` Richard Guenther
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 2:13 John David Anglin
2003-05-12 12:43 ` Diego Novillo
2003-05-15 17:50 ` John David Anglin
2003-05-15 19:32 ` Diego Novillo
2003-05-07 14:25 Diego Novillo
2003-05-07 14:30 ` Diego Novillo
2003-05-07 17:54 ` Qiong Cai
2003-05-07 18:02 ` law
2003-05-09 1:31 ` Qiong Cai
2003-05-09 2:02 ` Andrew Pinski
2003-05-07 18:24 ` Daniel Berlin
2003-05-08 5:51 ` Toon Moene
2003-05-08 13:26 ` Diego Novillo
2003-05-09 16:46 ` Gerald Pfeifer
2003-05-09 17:28 ` Diego Novillo
2003-05-09 17:37 ` Diego Novillo
2003-05-09 19:02 ` Eric Botcazou
2003-05-10 14:19 ` Gerald Pfeifer
2003-05-10 14:43 ` Graham Stott
2003-05-10 15:34 ` Daniel Berlin
2003-05-12 12:43 ` Diego Novillo
2003-05-10 15:04 ` Gerald Pfeifer
2003-05-12 14:21 ` Gerald Pfeifer
2003-05-12 16:27 ` Steven Bosscher
2003-05-20 10:44 ` Gerald Pfeifer
2003-05-20 11:39 ` Diego Novillo
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=E4499C0C-8481-11D7-87A1-000A95A34564@dberlin.org \
--to=dberlin@dberlin.org \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=rguenth@tat.physik.uni-tuebingen.de \
--cc=s.bosscher@student.tudelft.nl \
/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).