@0xAX The thing that really had me scratching my head at the time was that it had been like that for many, many years, and had run on a at least 100K Linux machines without issue.
@0xAX That's a great explanation. In fact I saw an occasional bug in some old code in a JNI library which turned out to be exactly this but only seemed to crop up when loaded in certain environments under Java 25. Fortunately, I was able to update the code it with a compiler intrinsic!
@ricursive@ZPostFacto@TrisH0x2A I think it needs to be read only and able to reason locally about it to stand a chance of hoisting: https://t.co/ej3OZmSVhx
Badger, badger, badger... MUSHROOM, MUSHROOM ๐
Jonti Picking's flash animation - and earworm - set the world alight in 2003, becoming one of the internet's most iconic memes. Now preserved in the BFI National Archive.
@0xC0DE6502@dennismars123 I see what you mean. 838 is particularly strange, given that the obvious would have been:
ldy #$00
lda #$02
That said, I mostly coded in a cartridge monitor for years as a teenager before I realised that an assembler would have made my life much easier! Who needs labels :)
@Gribeau@UridiumAuthor Assuming Windows API: it depends on the default minimum time resolution which I think is around ~15ms. I believe you can change it to be much lower (probably the millisecond you need).
@MartinPiper Thanks for sharing these! Apologies if you've already explained but I keep noticing that artifacts on the right seem to vanish just before they would have scrolled off screen, whereas those on the left seem to behave as I expect (e.g. 568 seconds in). Just curious about it ๐
@lefticus I experimented in asking LLMs to review code snippets involving raw pointers:
delete member_ptr;
member_ptr = nullptr;
member_ptr = new Object();
ChatGPT told me the middle line was superflous, and perplexity removed the middle line and then told me to add it!
@ninjadynamics@StirringDragon Last self modifying try *might* be 18 cycles if my brain isn't failing me:
STA RETRIEVE+1
LDA $20
STA BUBSY+1
RETRIEVE:
LDA #$00
STA $20
BUBSY:
LDA #$00
@lefticus So I'm really speculating here, but perhaps they use it when available by the DPMI host, but accept that since it may not be available they won't rely on it.
I admit I'm reaching well beyond my own understanding here ๐
@lefticus Maybe:
https://t.co/fG6wqD3Z4h "DPMI hosts which support virtual memory may also choose to ignore this function, but such hosts must be able to handle page faults transparently at arbitrary points during a client's execution, including within interrupt and exception handlers."