Re: Indicating function exit points in debug data

On Tue, 19 Mar 2019 at 22:40, Florian Weimer wrote: > * Justin Paston-Cooper: > > > On Tue, 19 Mar 2019 at 21:52, Florian Weimer wrote: > >> > >> * Justin Paston-Cooper: > >> > >> > On Tue, 19 Mar 2019 at 21:29, Florian Weimer > wrote: > >> >> > >> >> * Justin Paston-Cooper: > >> >> > >> >> > T

Re: Indicating function exit points in debug data

* Justin Paston-Cooper: > On Tue, 19 Mar 2019 at 21:52, Florian Weimer wrote: >> >> * Justin Paston-Cooper: >> >> > On Tue, 19 Mar 2019 at 21:29, Florian Weimer wrote: >> >> >> >> * Justin Paston-Cooper: >> >> >> >> > Tom Tromey suggested in that thread that this would be quite easy on >> >> > g

Re: Indicating function exit points in debug data

On Tue, 19 Mar 2019 at 21:52, Florian Weimer wrote: > > * Justin Paston-Cooper: > > > On Tue, 19 Mar 2019 at 21:29, Florian Weimer wrote: > >> > >> * Justin Paston-Cooper: > >> > >> > Tom Tromey suggested in that thread that this would be quite easy on > >> > gdb's side if gcc indicates exit loca

Re: Indicating function exit points in debug data

* Justin Paston-Cooper: > On Tue, 19 Mar 2019 at 21:29, Florian Weimer wrote: >> >> * Justin Paston-Cooper: >> >> > Tom Tromey suggested in that thread that this would be quite easy on >> > gdb's side if gcc indicates exit locations in the DWARF data, for >> > instance in the C case, it would ind

Re: Indicating function exit points in debug data

On Tue, 19 Mar 2019 at 21:29, Florian Weimer wrote: > > * Justin Paston-Cooper: > > > Tom Tromey suggested in that thread that this would be quite easy on > > gdb's side if gcc indicates exit locations in the DWARF data, for > > instance in the C case, it would indicate the locations of return > >

Re: Indicating function exit points in debug data

* Justin Paston-Cooper: > Tom Tromey suggested in that thread that this would be quite easy on > gdb's side if gcc indicates exit locations in the DWARF data, for > instance in the C case, it would indicate the locations of return > statements. On a related note, he mentions that the "finish" comm

Indicating function exit points in debug data

Hello, In my message https://sourceware.org/ml/gdb/2019-03/msg00042.html to the gdb mailing list, I asked whether it would be possible to implement a command which breaks at all exit points of the current stack frame. This would be very useful for evaluating a function's final state before it retu

Re: A bug in vrp_meet?

On 3/6/19 3:05 AM, Richard Biener wrote: > On Tue, Mar 5, 2019 at 10:36 PM Jeff Law wrote: >> >> On 3/5/19 7:44 AM, Richard Biener wrote: >> >>> So fixing it properly with also re-optimize_stmt those stmts so we'd CSE >>> the MAX_EXPR introduced by folding makes it somewhat ugly. >>> >>> Bootstrap