Re: [PATCH] Remove misleading debug line entries

2020-12-10 Thread Richard Biener
On Wed, 9 Dec 2020, Bernd Edlinger wrote: > On 12/8/20 7:57 PM, Bernd Edlinger wrote: > > On 12/8/20 11:35 AM, Richard Biener wrote: > >> > >> + { > >> + /* Remove a nonbind marker when the outer scope of the > >> + inline function is completely removed. */ > >> +

Re: [PATCH] Remove misleading debug line entries

2020-12-09 Thread Bernd Edlinger
On 12/8/20 7:57 PM, Bernd Edlinger wrote: > On 12/8/20 11:35 AM, Richard Biener wrote: >> >> + { >> + /* Remove a nonbind marker when the outer scope of the >> + inline function is completely removed. */ >> + if (gimple_debug_nonbind_marker_p (stmt) >> +

Re: [PATCH] Remove misleading debug line entries

2020-12-08 Thread Bernd Edlinger
On 12/8/20 11:35 AM, Richard Biener wrote: > > + { > + /* Remove a nonbind marker when the outer scope of the > + inline function is completely removed. */ > + if (gimple_debug_nonbind_marker_p (stmt) > + && BLOCK_ABSTRACT_ORIGIN (b)) > +

Re: [PATCH] Remove misleading debug line entries

2020-12-08 Thread Richard Biener
gt; tree-ssa-live.c change see below > > > > > > From 85b0e37d0c0d3ecac4908ebbfd67edc612ef22b2 Mon Sep 17 00:00:00 2001 > > From: Bernd Edlinger > > Date: Wed, 2 Dec 2020 12:32:02 +0100 > > Subject: [PATCH] Remove misleading debug line entries > > > > This remov

Re: [PATCH] Remove misleading debug line entries

2020-12-07 Thread Bernd Edlinger
22b2 Mon Sep 17 00:00:00 2001 > From: Bernd Edlinger > Date: Wed, 2 Dec 2020 12:32:02 +0100 > Subject: [PATCH] Remove misleading debug line entries > > This removes gimple_debug_begin_stmts without block info which remain > after a gimple block originating from an inline functio

Re: [PATCH] Remove misleading debug line entries

2020-12-07 Thread Richard Biener
GDB patch I want > to get applied, before debugging in optimized code will work > really a lot better than it used to be. > > I have now probably an acceptable patch, which addresses another > common cause why inlined functions end up without block info. > > That is a missing location info in a call stat

Re: [PATCH] Remove misleading debug line entries

2020-12-04 Thread Bernd Edlinger
mmon cause why inlined functions end up without block info. That is a missing location info in a call statement in ipa_param_body_adjustments::modify_call_stmt. What remains now, is just https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94474 yes it hit me a second time :-) These thunks do not have li

Re: [PATCH] Remove misleading debug line entries

2020-12-03 Thread Richard Biener
On Wed, 2 Dec 2020, Bernd Edlinger wrote: > On 12/2/20 8:50 AM, Richard Biener wrote: > > On Tue, 1 Dec 2020, Bernd Edlinger wrote: > > > >> Hi! > >> > >> > >> This removes gimple_debug stmts without block info after a > >> NULL INLINE_ENTRY. > >> > >> The line numbers from these stmts are from t

Re: [PATCH] Remove misleading debug line entries

2020-12-02 Thread Bernd Edlinger
> Richard. > >> >> Thanks >> Bernd. >> > From 1f97917fcbb15f7277dc9d6030dca05beab825c7 Mon Sep 17 00:00:00 2001 From: Bernd Edlinger Date: Wed, 2 Dec 2020 12:32:02 +0100 Subject: [PATCH] Remove misleading debug line entries This removes gimple_debug_begin_stmt

Re: [PATCH] Remove misleading debug line entries

2020-12-01 Thread Richard Biener
On Tue, 1 Dec 2020, Bernd Edlinger wrote: > Hi! > > > This removes gimple_debug stmts without block info after a > NULL INLINE_ENTRY. > > The line numbers from these stmts are from the inline function, > but since the inline function is completely optimized away, > there will be no DW_TAG_inlin

[PATCH] Remove misleading debug line entries

2020-12-01 Thread Bernd Edlinger
for trunk? Thanks Bernd. From 464867ca9b4cc6270fb6d41dc5346dc55395efb0 Mon Sep 17 00:00:00 2001 From: Bernd Edlinger Date: Fri, 13 Nov 2020 16:26:28 +0100 Subject: [PATCH] Remove misleading debug line entries This removes gimple_debug stmts without block info after a NULL INLINE_ENTRY. The line