Re: [PATCH] cleanup libgomp's coalesce chunk data structures

2018-12-28 Thread Thomas Schwinge
Hi! On Tue, 18 Dec 2018 11:07:07 +0100, Jakub Jelinek wrote: > On Tue, Dec 18, 2018 at 10:59:20AM +0100, Thomas Schwinge wrote: > > [...] > > Ok, thanks. Committed to trunk in r267446: commit 65c9e9f98bd9919ba1a93a87b7ebec4ab30283b2 Author: tschwinge Date: Fri Dec 28 11:33:54 2018 +

Re: [PATCH] cleanup libgomp's coalesce chunk data structures

2018-12-18 Thread Jakub Jelinek
On Tue, Dec 18, 2018 at 10:59:20AM +0100, Thomas Schwinge wrote: > OK for trunk? > > commit 20d3cbd6e27b10ae1cd352cc177d7697a4a57db0 > Author: Thomas Schwinge > Date: Mon Dec 17 18:26:29 2018 +0100 > > Cleanup libgomp's coalesce chunk data structures > > libgomp/ >

Re: [PATCH] cleanup libgomp's coalesce chunk data structures

2018-12-18 Thread Thomas Schwinge
Hi Jakub! Julian had a look at this, and now I too (and just fixed some formatting): On Wed, 2 May 2018 13:02:09 -0700, Cesar Philippidis wrote: > Libgomp's usage of struct gomp_coalesce_buf is a little confusing. The > member chunks is an array where the even elements represent the starting >

[PATCH] cleanup libgomp's coalesce chunk data structures

2018-05-02 Thread Cesar Philippidis
Libgomp's usage of struct gomp_coalesce_buf is a little confusing. The member chunks is an array where the even elements represent the starting address of the chunk cache line and the odd elements represent the corresponding ending addresses. This patch clarifies the usage of the chunks member by i