From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-478388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 18166 invoked by alias); 24 Feb 2015 22:30:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 16951 invoked by uid 48); 24 Feb 2015 22:30:52 -0000
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/58315] [4.8/4.9/5 Regression] Excessive memory use with -g
Date: Wed, 25 Feb 2015 00:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords: memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aoliva at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: aoliva at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58315-4-FLDqyBPHND@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58315-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58315-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-02/txt/msg02720.txt.bz2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58315

--- Comment #26 from Alexandre Oliva <aoliva at gcc dot gnu.org> ---
I had failed to measure peak memory use.  It went down from more than 4.8G to
less than 460M (vs 380MB without debug info).  Wheee!