public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54735] [4.8 Regression] Segmentation fault in walk_aliased_vdefs_1
Date: Fri, 28 Sep 2012 20:55:00 -0000 [thread overview]
Message-ID: <bug-54735-4-45WgNAlIM5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54735-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54735
--- Comment #4 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-09-28 20:55:22 UTC ---
(In reply to comment #3)
> r191747 should not increase the memory consumption. Instead, it'll only speedup
> compilation.
>
> I tried to compile the testcase without the patch, the memory consumption still
> increase, but very slowly (it took around 30 minutes to climb up to 1.8G)
Yes, please ignore my bogus bisection. Sorry.
I will let the testcase run overnight with r191747 reverted and
I guess it will also crash after a few hours.
next prev parent reply other threads:[~2012-09-28 20:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 12:54 [Bug tree-optimization/54735] New: " markus at trippelsdorf dot de
2012-09-28 13:08 ` [Bug tree-optimization/54735] " rguenth at gcc dot gnu.org
2012-09-28 19:30 ` markus at trippelsdorf dot de
2012-09-28 20:51 ` dehao at google dot com
2012-09-28 20:55 ` markus at trippelsdorf dot de [this message]
2012-09-29 7:06 ` markus at trippelsdorf dot de
2012-10-01 11:05 ` rguenth at gcc dot gnu.org
2012-10-01 15:31 ` markus at trippelsdorf dot de
2012-10-02 10:37 ` rguenth at gcc dot gnu.org
2012-10-02 11:17 ` rguenth at gcc dot gnu.org
2012-10-02 11:59 ` jamborm at gcc dot gnu.org
2012-10-02 12:08 ` markus at trippelsdorf dot de
2012-10-02 13:03 ` rguenth at gcc dot gnu.org
2012-10-04 11:48 ` rguenth at gcc dot gnu.org
2012-10-04 11:49 ` [Bug tree-optimization/54735] [4.7 " rguenth at gcc dot gnu.org
2012-11-26 14:26 ` rguenth at gcc dot gnu.org
2012-11-26 14:27 ` 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=bug-54735-4-45WgNAlIM5@http.gcc.gnu.org/bugzilla/ \
--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).