From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-481539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 114364 invoked by alias); 25 Mar 2015 06:26:37 -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 114290 invoked by uid 55); 25 Mar 2015 06:26:31 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65536] LTO line number information garbled
Date: Wed, 25 Mar 2015 07:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65536-4-OL6AkSAwqI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65536-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65536-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-03/txt/msg02683.txt.bz2

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

--- Comment #27 from Jan Hubicka <hubicka at ucw dot cz> ---
> I have in fact considered it already, since I think it should be fairly easy
> and it can be done incrementally. However, as always in GCC, things are never
> as trivial as they seem. I just tried following
> https://gcc.gnu.org/wiki/DebuggingGCC#Debugging_LTO to see what
> dump_line_table_statistics reports before and after my patch above, but it
> doesn't print the lto1 invokation. The debugx scripts
> (https://gcc.gnu.org/ml/gcc/2004-03/msg01195.html) do not seem to work with
> lto1 (why those scripts are not in contrib/?). I feel like a new contributor
> again! :)

I simply use --save-temps --verbose and use lto1 invocation from there. It is
easy ;)
Having direct way to invoke lto1 in gdb from gcc wrapper or script may come
handy,
but it is not that hard to do by hand.

Honza