TZUTC: -0700   
   MSGID: 56283.sync_sys@1:103/705 2b4488a0   
   PID: Synchronet 3.20a-Linux master/e93b6dfa6 Aug 22 202 GCC 12.2.0   
   TID: SBBSecho 3.20-Linux master/984c371ae Sep 06 2024 20:48 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   https://gitlab.synchro.net/main/sbbs/-/issues/782#note_5588   
      
   "Broken for loop optimization" is about what I was thinking at the time.   
   Forcing the variable to be logged (the "observer effect") made some loop   
   optimization impossible since the value had to be known and used then and   
   there.   
      
   The latter of my two commits introduced the log statement and I vaguely recall   
   this being the "real" fix, nothing to do with making the calculation inside   
   the square brackets, so I'm not surprised. In your case, I guess that   
   explicitly setting FFrameMaskIndex to 0 is the secret sauce, since zero is   
   zero and it doesn't need to be lazy about doing the math.   
      
   Of course, goodness knows what's going on in the guts of ye olden SpiderMonkey   
   on ARM. I'd love to have a better understanding of this so I can avoid   
   introducing similar problems in the future, but it's also annoying that   
   perfectly reasonable code just shits the bed unexpectedly.   
   --- SBBSecho 3.20-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 153/757 7715 154/10   
   SEEN-BY: 154/30 203/0 218/700 221/0 226/30 227/114 229/110 114 206   
   SEEN-BY: 229/317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 282/1038 291/111 292/8125 301/1 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888   
   SEEN-BY: 633/280 712/848 770/1 5020/400 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426