From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A4DF0385B831; Mon, 6 Apr 2020 11:58:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A4DF0385B831 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1586174292; bh=vHlM4KZkt+vUBt++MrmoEbe+zPh5gFsdU6qqqz4gicY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=im49de+sfufT4aqa9YIDblmDewytiYQgFHbzzZ4y4o+NWfsg0SGjF6KhTuDcaL+Wg 0jtBciph0w8voMgKdE+FRokYMk3LCdWdck4CWqAnpMreAZ1CsQueOo3Om/7htHjv1q D5wUybj+wb8vi6wm+DUyCvoBkbLhQd46PQvyFwIE= From: "rguenth 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 11:58:12 +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: rguenth 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 11:58:12 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94495 --- Comment #2 from Richard Biener --- Looks like ~20% for the first case so possibly worth investigating. I can = very well imagine we now less often run into some cut-offs and generate debug wh= ile we gave up previously.=