jump | 低配版 “ 跳一跳 ” ，基于Three.js - 低配版 “ 跳一跳 ” | Graphics library

You can do this efficiently with a dictionary:

So I use another library to solve this problem: OpenCV-python

We got have also the detection of segments( which are not disjoint) but with a hierarchy with the function findContours. The hierarchy is useful since the function detects different polygons. This implies no problems of connections we could have with the other method like explain in the post

Use syscall function code 3 to print doubles (not function code 2 — that's for single float).

Use mov.d to copy one register to another, e.g. into $f12 for sycalls (then no need to load 0.0 into $f0).

(Also, use l.d instead of ldc1.)

The loop: loop isn't a loop (there is no backward branch for it).

As @Peter says, your scaling/offsets are not properly accounting for the size of double, which is 8.  Scaling needs to multiply by 8 (shift by 3, not 2), and offsets need to be multiples of 8.

Your first loop, when its done, should not EXIT the program but rather continue with the next statement (i.e. the printing loop).

For this statement numbers[i+2] = numbers[i+1] + numbers[i]; there are two loads and one store as array references, whereas the assembly code is doing 3 loads and no store.

You use $s5, but never put anything in it.

The comparison of numbers[i+1] < 150 has to be done in (double) floating point, whereas the assembly code is attempting this in integer registers.

Floating point comparison is done using c.eq.d, c.lt.d, or c.le.d.  Like with integer compares, constants need to be in registers before the compare instruction.  150.0 would best come directly from memory (as a double constant) before the loop and remain there for the loop duration (or you can move integer 150 into a floating point register and convert that to double (cvt.w.d)).

Conditional branches on floating point compare conditions use either bc1t or bc1f (depending on the sense you want).

The C-like pseudo code probably doesn't run properly.  The exit condition for the first loop is suspect — it will probably run off the end of the array (depending on its initial data values).

Translating non-working C code into assembly is a recipe for frustration.  Suggest getting it working in C first; run it to make sure it works.

It is almost impossible to archive unless you enable RDP (which is very hard to archive if it was not the intention of the programmer).

You probably have screw-up the board design. You should have pull-up resistors on the debug lines and NRST connected to the programmer.

If you do not have NRST available simple solder the wire to the NRST, and when the programming probe connects to the uC, connect it to the GND.

If the NRST line is connected to the programmer you need to select nn the configuration "Connect under Reset"

If you read the assembler code from the top you will see that it reaches .L3, plus it also jumps to it with jne .L3, which is your for loop in C.

With JavaScript you can insert a space (' ') when you detect the contenteditable is empty. This pushes the caret position to the center.

You need an instance of class Rigidbody

loop through a 16 bit subtraction until the result is negative

"Branch" to Label if result is >0,

Do you see that these descriptions contradict each other?
The 1st one continues on 0, the 2nd one stops on 0.
Only you can decide which one is correct!

From a comment:

This code is part of a Bin to Ascii conversion, made by power of ten subtraction. The bin value could be >$8000, so it is 'negative' but this does not matter. In the first iteration I sub 10000 each cycle until the result is 'below 0', then I restore the previous value and continue with the remainder. The problem is how to detect the 'below 0' condition as said in the post

Next example subtracts 10000 ($2710) from the unsigned word stored at zero page address $90. The low byte is at $90, the high byte is at $91 (little endian).

Edit page2.html in both app.js post and html form action to page2