|
From: | Jörg F . Wittenberger |
Subject: | Re: [Chicken-users] remove enable/disable interrupt flag |
Date: | 30 Sep 2011 19:10:17 +0200 |
On Sep 30 2011, Alan Post wrote:
I think your point about signal being a wrapper around sigaction deserves to be repeated: it's my understanding too, and means that as it stands, my sigaction patch is essentially or completely a no-op on most platforms. Jerry's experience with it confusingly not-withstanding.
By all means: given the frequency and variations I'm testing theses days. Furthermore: even a wrapper could created minor differences in the actual execution sequence. Read: timing. To have or not to have it might be critical for the bug you are after to escape for some more time. Folklore along the way: once we ran into a gcc bug. It did show up rarely (but eventually too often) in RScheme's block allocation. (Turned out to be only at the then new AMD 64 due to bad instruction scheduling of gcc. The C code was valid.)
[Prev in Thread] | Current Thread | [Next in Thread] |