On Jan 30 19:11, Dan Bonachea wrote:
> On Wed, Jan 30, 2019 at 4:23 PM Corinna Vinschen
> wrote:
> > > > > Poking around further, I find that replacing the signal generation
> > > > > code in the test program for all cases with :
> > > > >
> > > > > pthread_kill(pthread_self(),sigid)
> > > > >
>
On Wed, Jan 30, 2019 at 4:23 PM Corinna Vinschen
wrote:
> > > > Poking around further, I find that replacing the signal generation
> > > > code in the test program for all cases with :
> > > >
> > > > pthread_kill(pthread_self(),sigid)
> > > >
> > > > generates compliant signal delivery behavior
On Jan 30 16:48, Corinna Vinschen wrote:
> On Jan 30 11:44, Corinna Vinschen wrote:
> > On Jan 29 18:21, Dan Bonachea wrote:
> > > > A minimal test program is copied below and also available here:
> > > > https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=589
> > >
> > > > It's worth noting POSIX
On Jan 30 11:44, Corinna Vinschen wrote:
> On Jan 29 18:21, Dan Bonachea wrote:
> > > A minimal test program is copied below and also available here:
> > > https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=589
> >
> > > It's worth noting POSIX 1003.1-2016 sec XRAT.B.2.4.1 (p.3577)
> > > specific
On Jan 29 18:21, Dan Bonachea wrote:
> > A minimal test program is copied below and also available here:
> > https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=589
>
> > It's worth noting POSIX 1003.1-2016 sec XRAT.B.2.4.1 (p.3577)
> > specifically requires that any given signal should be deliver
> A minimal test program is copied below and also available here:
> https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=589
> It's worth noting POSIX 1003.1-2016 sec XRAT.B.2.4.1 (p.3577)
> specifically requires that any given signal should be delivered to
> exactly one thread. Also the spec for a
On Tue, Jan 22, 2019 at 9:43 PM Dan Bonachea wrote:
>
> Hi Corinna and Madison, thanks for your responses.
>
> To clarify, I'm reasonably confident the problem I'm reporting has
> NOTHING to do with pthread_barrier. Our real application which
> exhibits very similar symptoms does not use pthread_b
Hi Corinna and Madison, thanks for your responses.
To clarify, I'm reasonably confident the problem I'm reporting has
NOTHING to do with pthread_barrier. Our real application which
exhibits very similar symptoms does not use pthread_barrier *at all*;
pthread_barrier was merely the most convenient/
On Sun, Jan 20, 2019 at 9:34 PM Dan Bonachea wrote:
>
> I'm writing to report some POSIX compliance problems with Cygwin
> signal handling in the presence of multiple pthreads that our group
> has encountered in our parallel scientific computing codes.
>
> A minimal test program is copied below and
On Jan 20 15:33, Dan Bonachea wrote:
> I'm writing to report some POSIX compliance problems with Cygwin
> signal handling in the presence of multiple pthreads that our group
> has encountered in our parallel scientific computing codes.
>
> A minimal test program is copied below and also available
10 matches
Mail list logo
