Re: [committed] Introduce dump_location_t

2018-06-29 Thread Richard Biener
On Thu, Jun 28, 2018 at 4:29 PM David Malcolm wrote: > > On Thu, 2018-06-28 at 13:29 +0200, Richard Biener wrote: > > On Tue, Jun 26, 2018 at 3:54 PM David Malcolm > > wrote: > > > > > > On Mon, 2018-06-25 at 15:34 +0200, Richard Biener wrote: > > > > On Wed, Jun 20, 2018 at 6:34 PM David Malcolm

Re: [committed] Introduce dump_location_t

2018-06-28 Thread David Malcolm
On Thu, 2018-06-28 at 13:29 +0200, Richard Biener wrote: > On Tue, Jun 26, 2018 at 3:54 PM David Malcolm > wrote: > > > > On Mon, 2018-06-25 at 15:34 +0200, Richard Biener wrote: > > > On Wed, Jun 20, 2018 at 6:34 PM David Malcolm > > m> > > > wrote: > > > > > > > > Here's v3 of the patch (one

Re: [committed] Introduce dump_location_t

2018-06-28 Thread Richard Biener
On Tue, Jun 26, 2018 at 3:54 PM David Malcolm wrote: > > On Mon, 2018-06-25 at 15:34 +0200, Richard Biener wrote: > > On Wed, Jun 20, 2018 at 6:34 PM David Malcolm > > wrote: > > > > > > Here's v3 of the patch (one big patch this time, rather than a > > > kit). > > > > > > Like the v2 patch kit,

[committed] Introduce dump_location_t

2018-06-26 Thread David Malcolm
On Mon, 2018-06-25 at 15:34 +0200, Richard Biener wrote: > On Wed, Jun 20, 2018 at 6:34 PM David Malcolm > wrote: > > > > Here's v3 of the patch (one big patch this time, rather than a > > kit). > > > > Like the v2 patch kit, this patch reuses the existing dump API, > > rather than inventing its