freenode/#sbcl - IRC Chatlog
Search
11:48:24
flip214
minion: memo for stassats: Please push your unwind-inspector into a contrib or so, slime could make use of that information
12:54:04
phoe
If I read the docstrings at https://github.com/sbcl/sbcl/blob/e98378ca004ef6d101b384f6c3130f24b7a1bc1f/src/code/serve-event.lisp#L215 correctly, then the call (SB-SYS:WAIT-UNTIL-FD-USABLE 7 :INPUT NIL NIL) has no timeout (will hang indefinitely).
12:54:34
phoe
I don't think that's the correct behavior in case of READ-CHAR-NO-HANG that shouldn't hang at all.
13:11:17
phoe
I think that this might be the race-condition issue that's been kicking me for the last two days.
13:21:12
minion
stassats, memo from flip214: Please push your unwind-inspector into a contrib or so, slime could make use of that information
13:23:05
pfdietz
I tried to reduce it past what the pruner could do, but you apply a broader range of simplifications, I think.
13:25:22
stassats
it looks like another instance of reoptimization not being triggered by changes that don't involve data flow
13:26:27
pfdietz
Well, whatever it is, any fix should wait until after freeze, especially if it's not a recent regression.
13:27:33
stassats
your particular form does not fail it inserts type checks and the old code reoptimizes the whole thing in that case
13:29:15
stassats
but there's more question, it stops optimizing, yet the IR1 is consistent at that point
13:30:12
pfdietz
I wonder if it would be useful to write a random ir1 generator, to better exercise the later code.
13:32:02
stassats
if we do inconsistent things to the IR but there's nobody to hear it, does it make a sound?
13:32:46
pfdietz
Understood. The issue is that bugs in later code can be latent because the earlier passes don't produce inputs that would stimulate them. Changes to the earlier passes, even if correct in themselves, can then activate those bugs.