Still 100% factually accurate.

Yeah, the simplest way is gonna be to adjust the pointers so that you can use the same index value for both; in the provided example, if you add 47 to the pointer value in RP0, you can loop through index values 0-7 for both.

Also, if you are having one state switch, you can make it to be just jump_table, so instead of lot of cmp #... you just jump to address at table[state] :)
^ That. Turns the dispatch into a constant-time operation instead of an O(<= N) one, and allows you to separate the state routines from the ...

Hard disagree - even clumsy personal art is much more interesting to look at than generic machine output, and I much prefer your DIY example.

If you're trying to test/measure, a 24-bit PRNG has a maximum sequence length of "only" 16.7 million values, which is well within the realm of generating & caching for analysis on modern machines.

I don't know enough about this stuff to say about the algorithm in question, but if it's vulnerable to the same "all zeros = frozen state" issue as LFSRs are, you wanna be careful injecting arbitrary "noise" values into it - maybe take the timer value and OR it with the PRNG state rather than ...

If you're juggling more than just interrupt-service stuff alongside your Big Intensive Background Task, and you don't want to have to modify that, there's about two ways I can see for you to go:

A. Have your interrupt service, upon completion, pass control to any active "medium-priority" tasks ...

(It occurs that, if you're using a linked-list-of-chunks structure, making the chunks 256 bytes cuts your pointer size in half.)

Obviously a tradeoff between frequent operations being quick, because local, but possibly causing fragmentation, and then the other half of the solution, which is to defragment.
Fragmentation could be also be addressed (!) when the user saves his/her work, or if a timed-save feature is implemented ...

I'm curious where else this term was used besides x86-land! I'd go with "paragraph" for familiarity's sake, but if not, "sentence" seems a fitting choice

For another project and a slightly different purpose (breaking out half of a dual op-amp from a PCB that only uses the one) I picked up an IC socket with extra-long pins, so that I could stack the IC on a piece of stripboard above the rest of the project and run wires to the relevant pins without ...

Interesting notion - simple jump/branch loops should be easy to directly detect, as well (if a JMP points back to itself, or a branch if the branch is taken,) though I don't know how much it'd save you over the heuristic you've already established. This won't be 100% cycle-accurate as interrupt ...

I need to have a go at this myself sometime. The solution I've considered for storing in a way that makes insertion and block operations less expensive is to use a linked list of fixed-size chunks that can hold from zero to N characters - you lose some of your available text space to overhead, but ...

It's all very strange.
A huge part of the explanation for the very strange behavior of modern first-world economies is that we've entered the terminal phase of a long spiral where every business of consequential size is run by decision-makers with no actual knowledge of the line of work, whose ...

The amount of armchair quarterbacking here from people who are either long retired or in the end stages of a long and established career is honestly a little maddening. I don't mean that as a diss against the older members here, but if you haven't actually been looking for work in the last fifteen ...