public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/58315] New: [4.8/4.9 Regression] Excessive memory use with -g
Date: Wed, 04 Sep 2013 12:25:00 -0000 [thread overview]
Message-ID: <bug-58315-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58315
Bug ID: 58315
Summary: [4.8/4.9 Regression] Excessive memory use with -g
Product: gcc
Version: 4.8.1
Status: UNCONFIRMED
Keywords: memory-hog
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Compiling the PPL testsuite, specifically MIP_Problem/mipproblem1.cc, with
-O2 -g makes GCC use nearly 6GB of memory (followed by GAS needing 6.5GB
of memory to assemble the result).
Dropping -g results in instant gratification.
next reply other threads:[~2013-09-04 12:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 12:25 rguenth at gcc dot gnu.org [this message]
2013-09-04 12:25 ` [Bug debug/58315] " rguenth at gcc dot gnu.org
2013-09-04 12:26 ` rguenth at gcc dot gnu.org
2013-09-04 12:40 ` rguenth at gcc dot gnu.org
2013-09-11 11:40 ` rguenth at gcc dot gnu.org
2013-10-16 9:51 ` jakub at gcc dot gnu.org
2013-11-22 10:54 ` rguenth at gcc dot gnu.org
2014-05-22 9:03 ` [Bug debug/58315] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:31 ` [Bug debug/58315] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-02-19 21:49 ` aldyh at gcc dot gnu.org
2015-02-19 22:52 ` aldyh at gcc dot gnu.org
2015-02-20 8:21 ` rguenth at gcc dot gnu.org
2015-02-20 16:31 ` aldyh at gcc dot gnu.org
2015-02-20 16:58 ` rguenth at gcc dot gnu.org
2015-02-20 17:06 ` rguenth at gcc dot gnu.org
2015-02-20 17:36 ` aldyh at gcc dot gnu.org
2015-02-20 23:10 ` aldyh at gcc dot gnu.org
2015-02-21 3:13 ` aldyh at gcc dot gnu.org
2015-02-23 22:59 ` aldyh at gcc dot gnu.org
2015-02-23 23:01 ` aldyh at gcc dot gnu.org
2015-02-24 7:52 ` aldyh at gcc dot gnu.org
2015-02-24 9:09 ` jakub at gcc dot gnu.org
2015-02-24 9:18 ` rguenther at suse dot de
2015-02-24 16:32 ` aldyh at redhat dot com
2015-02-24 16:42 ` jakub at gcc dot gnu.org
2015-02-24 17:17 ` aldyh at redhat dot com
2015-02-24 18:19 ` jakub at gcc dot gnu.org
2015-02-24 22:47 ` aoliva at gcc dot gnu.org
2015-02-25 0:36 ` aoliva at gcc dot gnu.org
2015-02-25 10:21 ` rguenth at gcc dot gnu.org
2015-02-25 16:45 ` jason at gcc dot gnu.org
2015-05-27 15:36 ` [Bug debug/58315] [4.8/4.9/5/6 " redflames1003 at gmail dot com
2015-05-27 19:49 ` jason at gcc dot gnu.org
2015-06-09 5:05 ` aoliva at gcc dot gnu.org
2015-06-09 5:14 ` aoliva at gcc dot gnu.org
2015-06-09 5:20 ` [Bug debug/58315] [4.8/4.9/5 " aoliva at gcc dot gnu.org
2015-07-16 9:16 ` [Bug debug/58315] [4.9/5 " rguenth at gcc dot gnu.org
2015-10-07 17:33 ` redflames1003 at gmail dot com
2015-10-10 11:24 ` aoliva at gcc dot gnu.org
2015-10-10 12:06 ` aoliva at gcc dot gnu.org
2015-10-10 12:07 ` aoliva at gcc dot gnu.org
2015-10-13 13:57 ` redflames1003 at gmail dot com
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-58315-4@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).