> -----Original Message-----
> From: Prathamesh Kulkarni <[email protected]>
> Sent: 16 February 2026 19:06
> To: Tobias Burnus <[email protected]>; Matthew Malcomson
> <[email protected]>; [email protected]
> Subject: RE: [PATCH 2/5] libgomp: Ensure memory sync after performing
> tasks
> 
> External email: Use caution opening links or attachments
> 
> 
> > -----Original Message-----
> > From: Prathamesh Kulkarni
> > Sent: 31 January 2026 10:35
> > To: 'Prathamesh Kulkarni' <[email protected]>; Tobias Burnus
> > <[email protected]>; Matthew Malcomson <[email protected]>;
> > [email protected]
> > Subject: RE: [PATCH 2/5] libgomp: Ensure memory sync after
> performing
> > tasks
> >
> >
> >
> > > -----Original Message-----
> > > From: Prathamesh Kulkarni <[email protected]>
> > > Sent: 20 January 2026 09:48
> > > To: Tobias Burnus <[email protected]>; Matthew Malcomson
> > > <[email protected]>; [email protected]; Jakub Jelinek
> > > <[email protected]>
> > > Cc: Thomas Schwinge <[email protected]>; Andrew Stubbs
> > > <[email protected]>; Tom de Vries <[email protected]>; Sebastian
> Huber
> > > <[email protected]>
> > > Subject: RE: [PATCH 2/5] libgomp: Ensure memory sync after
> > performing
> > > tasks
> > >
> > > External email: Use caution opening links or attachments
> > >
> > >
> > > > -----Original Message-----
> > > > From: Tobias Burnus <[email protected]>
> > > > Sent: 20 January 2026 02:39
> > > > To: Prathamesh Kulkarni <[email protected]>; Matthew
> > Malcomson
> > > > <[email protected]>; [email protected]; Jakub Jelinek
> > > > <[email protected]>
> > > > Cc: Thomas Schwinge <[email protected]>; Andrew Stubbs
> > > > <[email protected]>; Tom de Vries <[email protected]>; Sebastian
> > Huber
> > > > <[email protected]>
> > > > Subject: Re: [PATCH 2/5] libgomp: Ensure memory sync after
> > > performing
> > > > tasks
> > > >
> > > > External email: Use caution opening links or attachments
> > > >
> > > >
> > > > Hi Prathamesh,
> > > >
> > > > Prathamesh Kulkarni wrote:
> > > > > The attached patch similarly adds target pragmas to the test
> as
> > > > previous patch.
> > > > > Does it look OK ?
> > > >
> > > > Thanks for revising Matthew's patch.
> > > >
> > > > Yes, LGTM. – However, except for 'Daily bump.', it seems to be
> > > > uncommon to have a '.' at the end of the first line (summary) of
> > the
> > > > git commit; hence, consider removing it.
> > > Thanks, adjusted the commit summary and committed to trunk in:
> > >
> >
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=304d08fea9e68c5b48065328
> > > 16b58d33a15a917d
> > Hi Tobias,
> > Sorry I messed up the newly added test (pr122356.c) while
> committing,
> > and Linaro CI reported the test failing:
> > https://linaro.atlassian.net/browse/GNU-1822
> >
> > This happens because full_data is not initialized to 0 on second
> call
> > to test() on host, which results in call to abort.
> > The attached patch modifies pr122356.c (and similarly pr122314.c) to
> > initialize full_data to 0 at beginning of test().
> >
> > With patch, running make check-target-libgomp
> > RUNTESTFLAGS="c.exp=pr122356.c" shows:
> >
> >                 === libgomp Summary ===
> > # of expected passes            2
> >
> > OK to commit ?
> Hi,
> ping: https://gcc.gnu.org/pipermail/gcc-patches/2026-
> January/707277.html
Hi,
ping * 2: https://gcc.gnu.org/pipermail/gcc-patches/2026-January/707277.html

Rainer confirmed the patch fixes the test failure at his end:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124123#c2

Thanks,
Prathamesh
> 
> Thanks,
> Prathamesh
> >
> > Thanks,
> > Prathamesh
> > >
> > > Thanks,
> > > Prathamesh
> > > >
> > > > Tobias

Reply via email to