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 middle-end/52097] ICE: in get_bit_range, at expr.c:4535 with -O -flto -fexceptions -fnon-call-exceptions --param allow-store-data-races=0
Date: Tue, 14 Feb 2012 15:52:00 -0000 [thread overview]
Message-ID: <bug-52097-4-LEIzsC3kAw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52097-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52097
Markus Trippelsdorf <markus at trippelsdorf dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markus at trippelsdorf dot
| |de
--- Comment #7 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-02-14 15:50:12 UTC ---
(In reply to comment #6)
> Would be interesting to see what the attached patch does to memory usage
> with Mozilla though (the Fortran issue is really latent, still changing this
> during stage4 seems risky at least - SPEC 2k6 survived a LTO build/run though).
Not much difference in my testing (PGO+LTO Firefox built):
without patch:
2.5 GB written out
~4.5 GB memory usage (5GB peak)
with your patch:
2.4 GB written out
memory usage roughly the same as before.
next prev parent reply other threads:[~2012-02-14 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 20:02 [Bug middle-end/52097] New: " zsojka at seznam dot cz
2012-02-03 10:10 ` [Bug middle-end/52097] " rguenth at gcc dot gnu.org
2012-02-14 1:11 ` aldyh at gcc dot gnu.org
2012-02-14 9:04 ` rguenther at suse dot de
2012-02-14 10:09 ` rguenth at gcc dot gnu.org
2012-02-14 13:23 ` rguenth at gcc dot gnu.org
2012-02-14 14:01 ` rguenth at gcc dot gnu.org
2012-02-14 15:52 ` markus at trippelsdorf dot de [this message]
2012-03-06 9:54 ` rguenth at gcc dot gnu.org
2012-03-06 9:57 ` rguenth at gcc dot gnu.org
2012-03-08 7:56 ` krebbel at gcc dot gnu.org
2012-03-08 8:27 ` pinskia at gcc dot gnu.org
2012-03-14 11:03 ` rguenth at gcc dot gnu.org
2012-06-04 8:43 ` rguenth at gcc dot gnu.org
2013-02-19 20:38 ` LpSolit at netscape dot net
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-52097-4-LEIzsC3kAw@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).