public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/39222] out of memory bootstrapping
[not found] <bug-39222-4@http.gcc.gnu.org/bugzilla/>
@ 2012-02-22 13:35 ` xiaoyuanbo at yeah dot net
0 siblings, 0 replies; 6+ messages in thread
From: xiaoyuanbo at yeah dot net @ 2012-02-22 13:35 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39222
xiaoyuanbo <xiaoyuanbo at yeah dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xiaoyuanbo at yeah dot net
--- Comment #6 from xiaoyuanbo <xiaoyuanbo at yeah dot net> 2012-02-22 12:57:32 UTC ---
total root
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/39222] out of memory bootstrapping
2009-02-17 21:09 [Bug target/39222] New: " aj at gcc dot gnu dot org
` (3 preceding siblings ...)
2009-02-18 10:18 ` aj at gcc dot gnu dot org
@ 2009-02-18 10:46 ` jakub at gcc dot gnu dot org
4 siblings, 0 replies; 6+ messages in thread
From: jakub at gcc dot gnu dot org @ 2009-02-18 10:46 UTC (permalink / raw)
To: gcc-bugs
------- Comment #5 from jakub at gcc dot gnu dot org 2009-02-18 10:46 -------
But not on the same source, but different one (insn-recog.c grew because of
that change).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39222
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/39222] out of memory bootstrapping
2009-02-17 21:09 [Bug target/39222] New: " aj at gcc dot gnu dot org
` (2 preceding siblings ...)
2009-02-18 8:55 ` jakub at gcc dot gnu dot org
@ 2009-02-18 10:18 ` aj at gcc dot gnu dot org
2009-02-18 10:46 ` jakub at gcc dot gnu dot org
4 siblings, 0 replies; 6+ messages in thread
From: aj at gcc dot gnu dot org @ 2009-02-18 10:18 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from aj at gcc dot gnu dot org 2009-02-18 10:17 -------
Increasing ulimit from 1000000 to 1100000 (10 %!) did not help, increasing it
to 1200000 helped.
So, we have now hit quite some increase of memory usage with just this single
commit and not just a few bytes...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39222
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/39222] out of memory bootstrapping
2009-02-17 21:09 [Bug target/39222] New: " aj at gcc dot gnu dot org
2009-02-17 21:10 ` [Bug target/39222] " aj at gcc dot gnu dot org
2009-02-18 7:15 ` ubizjak at gmail dot com
@ 2009-02-18 8:55 ` jakub at gcc dot gnu dot org
2009-02-18 10:18 ` aj at gcc dot gnu dot org
2009-02-18 10:46 ` jakub at gcc dot gnu dot org
4 siblings, 0 replies; 6+ messages in thread
From: jakub at gcc dot gnu dot org @ 2009-02-18 8:55 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from jakub at gcc dot gnu dot org 2009-02-18 08:54 -------
Yeah, with ulimit you can always pick some limit almost any change might go
over. As a bug should be only considered if memory usage increases a lot,
daily tiny increases and decreases in memory usage aren't a bug.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39222
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/39222] out of memory bootstrapping
2009-02-17 21:09 [Bug target/39222] New: " aj at gcc dot gnu dot org
2009-02-17 21:10 ` [Bug target/39222] " aj at gcc dot gnu dot org
@ 2009-02-18 7:15 ` ubizjak at gmail dot com
2009-02-18 8:55 ` jakub at gcc dot gnu dot org
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: ubizjak at gmail dot com @ 2009-02-18 7:15 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from ubizjak at gmail dot com 2009-02-18 07:15 -------
The commit you are referring to just hit the nail on the road and gets over
your memory threshold. The blockage insertion is enabled only for
-fno-omit-frame-pointer.
Even if we revert this patch (very unlikely, since it fixes real problem),
memory consumption will go over your threhold as soon as somebody adds a couple
of patterns to the md file.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39222
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/39222] out of memory bootstrapping
2009-02-17 21:09 [Bug target/39222] New: " aj at gcc dot gnu dot org
@ 2009-02-17 21:10 ` aj at gcc dot gnu dot org
2009-02-18 7:15 ` ubizjak at gmail dot com
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: aj at gcc dot gnu dot org @ 2009-02-17 21:10 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from aj at gcc dot gnu dot org 2009-02-17 21:10 -------
Created an attachment (id=17316)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17316&action=view)
insn-recog.i
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39222
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-02-22 13:34 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-39222-4@http.gcc.gnu.org/bugzilla/>
2012-02-22 13:35 ` [Bug target/39222] out of memory bootstrapping xiaoyuanbo at yeah dot net
2009-02-17 21:09 [Bug target/39222] New: " aj at gcc dot gnu dot org
2009-02-17 21:10 ` [Bug target/39222] " aj at gcc dot gnu dot org
2009-02-18 7:15 ` ubizjak at gmail dot com
2009-02-18 8:55 ` jakub at gcc dot gnu dot org
2009-02-18 10:18 ` aj at gcc dot gnu dot org
2009-02-18 10:46 ` jakub at gcc dot gnu dot org
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).