public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39301] ICE in register_overhead, at bitmap.c:115
Date: Tue, 31 Mar 2009 05:46:00 -0000 [thread overview]
Message-ID: <20090331054625.32538.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39301-271@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from bje at gcc dot gnu dot org 2009-03-31 05:46 -------
I still cannot reproduce this using the 4.4 branch:
$ ./xgcc -v
Reading specs from ./specs
Target: powerpc64-unknown-linux-gnu
Configured with: /home/bje/source/gcc-clean/configure --enable-languages=c
--enable-gather-detailed-mem-stats --with-cpu=default64 --disable-bootstrap
--quiet
Thread model: posix
gcc version 4.4.0 20090327 (experimental) [trunk revision 145326] (GCC)
$ ./cc1 -I../include -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2
-O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing
-fwrapv -fomit-frame-pointer -fPIC -fno-common compiler.i
btowc wctob mbrlen code_size ___H__20_compiler_2e_o1 {GC 124407k -> 67811k}
___init_proc ____20_compiler_2e_o1
Analyzing compilation unit
{GC 107701k -> 81846k}Performing interprocedural optimizations
<visibility> <early_local_cleanups> {GC 140505k -> 139614k} <summary generate>
<inline> <static-var> <pure-const>Assembling functions:
code_size ___init_proc ____20_compiler_2e_o1 ___H__20_compiler_2e_o1 {GC
188952k -> 155976k} {GC 232824k -> 158800k}
cc1: out of memory allocating 4064 bytes after a total of 3485597696 bytes
Can you see any differences here?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39301
next prev parent reply other threads:[~2009-03-31 5:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 14:03 [Bug c/39301] New: " lucier at math dot purdue dot edu
2009-02-25 14:11 ` [Bug c/39301] " rguenth at gcc dot gnu dot org
2009-03-23 4:59 ` [Bug middle-end/39301] " bje at gcc dot gnu dot org
2009-03-27 4:15 ` bje at gcc dot gnu dot org
2009-03-27 15:12 ` lucier at math dot purdue dot edu
2009-03-31 5:46 ` bje at gcc dot gnu dot org [this message]
2009-03-31 12:38 ` lucier at math dot purdue dot edu
2009-05-08 20:28 ` lucier at math dot purdue dot edu
2009-05-14 1:32 ` bje at gcc dot gnu dot org
2009-05-15 21:55 ` lucier at math dot purdue dot edu
2009-05-15 21:57 ` lucier at math dot purdue dot edu
2009-05-15 22:29 ` rguenth at gcc dot gnu dot org
2009-05-16 1:21 ` lucier at math dot purdue dot edu
2009-05-16 10:26 ` rguenth at gcc dot gnu dot org
2009-05-16 14:37 ` lucier at math dot purdue dot edu
2009-05-16 22:42 ` hjl at gcc dot gnu dot org
2009-05-17 1:09 ` lucier at math dot purdue dot edu
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=20090331054625.32538.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).