[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops
From: |
felix . winkelmann |
Subject: |
Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops |
Date: |
Wed, 28 Aug 2019 22:42:57 +0200 |
>
> Théo Cavignac <address@hidden> writes:
>
> > Erratum: I think it did fix the bug, I just misunderstood a different
> > error. Is this modification of coops config viable for upstream or should I
> > find a way to grant thread safety in my own code ?
> >
>
> Great!
>
> I see Felix is going to add the -disable-interrupts flag to the coops
> egg.
>
> However, you may still need to compile your code that defines
> coops thigs with -disable-interrupts. There are some macros in coops
> that define complex functions. Those may still be non-thread safe.
The macros are all defining forms or used internally (mostly the
sinister "build-cache"), so I don't see a need for that.
But, will all things multithreaded, you can of course never be sure...
felix
- [Chicken-users] Obscure bug with srfi-18, mailbox and coops, Théo Cavignac, 2019/08/28
- [Chicken-users] Obscure bug with srfi-18, mailbox and coops, Théo Cavignac, 2019/08/28
- Message not available
- Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops, Théo Cavignac, 2019/08/28
- Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops, Théo Cavignac, 2019/08/28
- Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops, megane, 2019/08/28
- Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops, Théo Cavignac, 2019/08/28
- Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops,
felix . winkelmann <=
- Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops, felix . winkelmann, 2019/08/28
- Message not available