So using 128bits instructions would imply you had 'words' which were over 16 characters long on average, right?
The average (english) word is ~5 characters long, so most of the time, you'd be forced to check anyway.
The average (english) word is ~5 characters long, so most of the time, you'd be forced to check anyway.
That said, while it may not be a solution for every case, it's a solution for the common case and a starting point for other cases, and thus pretty nifty and potentially useful.
Maybe do it log> 1) check if you can jump 16, 2) check if you can jump 8, 3) check if you can jump 4, execute
The scalar operations of reading a character, checking whether it's a space (0x20), and writing it to an output can often be done in a single cycle (the processor is 'superscalar'). A mispredicted branch costs about 15 cycles. Thus for simple tasks like this, if the average distance between spaces is 16 or less, you are likely better off with the simpler straightforward approach.