From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4B0BC3951455; Mon, 6 Apr 2020 08:01:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4B0BC3951455 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1586160090; bh=zxkqP98Eb7xuIyXYkEUTqRsUhOO3WBfQ5tjRjgTbOCU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Z83+hFu1SglSJFzw1H6HVHwCViQ54emQeg8f3jD5iYG43/+hwKP4aKQDp6X7r4PP2 l5cg/xBEW3e5KEe1kqH4VqWOlsc2iXm9V01wciJXUBe395Ivmbiq8LyT7UyRHyYhms XVvldsLPc8lzBvJgH/M7z4xESBq7wJhHaDP2PU1M= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/94495] [10 Regression] Debug info size growth since r10-7515-g2c0fa3ecf70d199a Date: Mon, 06 Apr 2020 08:01:30 +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: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Apr 2020 08:01:30 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94495 --- Comment #1 from Jakub Jelinek --- The numbers I got is that something grew up a little bit, something shrunk a little bit, sometimes .debug_info grew up and .debug_loc shrunk, sometimes = the other way around, but in general it wasn't significant. Debug info size growth in itself is not something bad if it means better variable location coverage, on the other size shrinking is something bad if= it means fewer variables are covered or on a smaller set of instructions.=