On 26 March 2013 11:01, Simon Toedt <[email protected]> wrote:
> I have a request:
> While AST and UWIN are awesome it'll be nice to have more detailed,
> uptodate documentation with examples. Please don't be offended but
> there are many great things in AST and UWIN which are little known
> because the documentation is, well, very RISC-like.

Well, what can I say? David and Glenn are researchers and run AST and
UWIN like a research project. What's needed here is someone else who
writes documentation from a programmers pov.
>
> Simon
>
> ---------- Forwarded message ----------
> From: Simon Toedt <[email protected]>
> Date: Tue, Mar 26, 2013 at 10:29 AM
> Subject: Re: [ast-developers] Signal trap loop behaviour...
> To: Glenn Fowler <[email protected]>
> Cc: [email protected], [email protected],
> [email protected]
>
>
> On Wed, Mar 20, 2013 at 4:19 AM, Glenn Fowler <[email protected]> wrote:
>>
>> On Wed, 20 Mar 2013 02:13:25 +0100 Roland Mainz wrote:
>>> BTW: I forgot to explain why I suggested a single-linked list as FIFO
>>> queue... the idea is to _not_ disable signals when the siginfo is
>>> processed in the signal callback... instead signals can be received
>>> even while the signal callback is processed... this is safe as long
>>> the insertion into the single-linked list is done using atomic
>>> instructions ([1]).
>>
>>> [1]=Erm... Glenn: (Without digging around) Does ASO have a
>>> compare-and-swap for pointers ?
>>
>>         void*           asocasptr(void volatile*, void*, void*);
>>
>> and its documented!
>
> Where is it documented? The only reference I found is
> http://www2.research.att.com/~gsf/man/man3/aso.html which only lists
> its name but no usage example or further description which flavor of
> CAS is implemented.
>
> Simon
> _______________________________________________
> ast-developers mailing list
> [email protected]
> http://lists.research.att.com/mailman/listinfo/ast-developers


Ced
-- 
Cedric Blancher <[email protected]>
Institute Pasteur
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers

Reply via email to