Build breakage

2023-12-13 Thread Jerry D
I am getting this failure to build from clean trunk. In file included from ../../../../trunk/libgomp/config/linux/allocator.c:31: ../../../../trunk/libgomp/config/linux/allocator.c: In function ‘linux_memspace_alloc’: ../../../../trunk/libgomp/config/linux/allocator.c:70:26: error: format ‘%ld’

Re: Build breakage

2023-12-13 Thread Thomas Schwinge
Hi! On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote: > I am getting this failure to build from clean trunk. This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172f6bdd "libgomp: basic pinned memory on Linux", which supposedly was only tested with '--disable-multilib' or so. As A

Fix 'libgomp/config/linux/allocator.c' 'size_t' vs. '%ld' format string mismatch (was: Build breakage)

2023-12-13 Thread Thomas Schwinge
Hi! On 2023-12-13T20:36:40+0100, I wrote: > On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote: >> I am getting this failure to build from clean trunk. > > This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172f6bdd > "libgomp: basic pinned memory on Linux", which supposedly was only

Re: Build breakage

2023-12-13 Thread Jonathan Wakely
On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote: > Hi! > > On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote: > > I am getting this failure to build from clean trunk. > > This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172f6bdd > "libgomp: basic pinned memory on Linux", which

RE: [PATCH v7] libgfortran: Replace mutex with rwlock

2023-12-13 Thread Thomas Schwinge
Hi Lipeng! On 2023-12-12T02:05:26+, "Zhu, Lipeng" wrote: > On 2023/12/12 1:45, H.J. Lu wrote: >> On Sat, Dec 9, 2023 at 7:25 PM Zhu, Lipeng wrote: >> > On 2023/12/9 23:23, Jakub Jelinek wrote: >> > > On Sat, Dec 09, 2023 at 10:39:45AM -0500, Lipeng Zhu wrote: >> > > > This patch try to intro

Re: Build breakage

2023-12-13 Thread Thomas Schwinge
Hi! On 2023-12-13T20:27:44+, Jonathan Wakely wrote: > On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote: >> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote: >> > I am getting this failure to build from clean trunk. >> >> This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172

Re: Build breakage

2023-12-13 Thread Jonathan Wakely
On Wed, 13 Dec 2023 at 20:56, Thomas Schwinge wrote: > > Hi! > > On 2023-12-13T20:27:44+, Jonathan Wakely wrote: > > On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote: > >> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote: > >> > I am getting this failure to build from clean trunk. > >> >

RE: [PATCH v7] libgfortran: Replace mutex with rwlock

2023-12-13 Thread Zhu, Lipeng
On 2023/12/14 4:52, Thomas Schwinge wrote: > Hi Lipeng! > > On 2023-12-12T02:05:26+, "Zhu, Lipeng" wrote: > > On 2023/12/12 1:45, H.J. Lu wrote: > >> On Sat, Dec 9, 2023 at 7:25 PM Zhu, Lipeng > wrote: > >> > On 2023/12/9 23:23, Jakub Jelinek wrote: > >> > > On Sat, Dec 09, 2023 at 10:39:45

[committed] testsuite: Fix up target-enter-data-1.c on 32-bit targets

2023-12-13 Thread Jakub Jelinek
On Wed, Nov 29, 2023 at 11:43:05AM +, Julian Brown wrote: > * c-c++-common/gomp/target-enter-data-1.c: Adjust scan output. struct bar { int num_vectors; double *vectors; }; is 16 bytes only on 64-bit targets, on 32-bit ones it is just 8 bytes, so the explicit matching of the * 16 multip