hypr | Build UI components with reactive state | Reactive Programming library

It looks like you're trying to use a C compiler to compile a C++ program (or a program which uses a C++ library). That isn't going to work without a lot of effort, since the C compiler doesn't know where to find the C++ standard libraries and other libraries for things such as exception handling.

You haven't posted your Makefile, but if you're using the variable CC to compile and link your code, try switching to using CXX, which is the C++ compiler instead.

my OS is 16 bit, but when I try to use 16 bit registers in my compare function it tells me that I am giving it an invalid effective address.

16-bit addressing modes can only use [bx|bp + si|di + constant] or a subset of that. Using 32-bit addressing modes is a valid workaround if you can't just pass pointers in si and di for addr modes like [si] and [di] like a normal person.

But only if you zero-extend the 16-bit addresses into the full 32-bit register, otherwise high garbage can lead to a segment limit violation. In real mode, segments implicitly have a 64k limit; offset > 65535 will fault.

You're probably not actually crashing VirtualBox itself, but you could be crashing the virtual guest machine with a triple fault or something.

mov eax, msg_welcome does write the full register with the zero-extended address, unlike mov si, msg_welcome

Your loop will always exit after the first iteration, because inc ecx / je .zero_test falls through. INC clears ZF because incrementing ECX from 0 to 1 leaves ECX != 0.

Presumably you should inc before cmp/je if you want je to read flags set by cmp.

I'm not sure where your code would actually fault. Use a debugger to find out, e.g. by running it inside BOCHS instead of VirtualBox. BOCHS has a debugger built-in which understands segmentation, unlike attaching GDB to qemu or virtualbox as a GDB-remote.

Your loop is pretty inefficient, BTW. You can use cmp dl, [di] or something and put a jne at the bottom. If you break out of the loop with a cmp/jcc, you can put a test dl,dl/jnz as the loop branch at the bottom.

You should never write a jcc over a jmp, just write a JCC with the opposite condition that falls through. And here you can fall through to a RET instead of a jmp .done. (The one exception is if you have to jump farther than -128..+127 bytes, and you're targeting an ancient CPU that doesn't support JCC rel16, only short JCC rel8.)

On an AMD CPU (no partial-register renaming), mov dh, [mem] has a false dependency on mov dl, [mem], so there's extra latency for merging the load values before your cmp can run. That's another reason for using a cmp-with-mem instead of 2 loads.

(Spyder maintainer here) Since Spyder 3.3.1 (to be released in a couple of days), the solution is the following:

1. Activate your environment

2. Install the spyder-kernels package there, with the following command:

   conda install spyder-kernels=0.*

3. Also run there (in a system terminal)

   python -c "import sys; print(sys.executable)"

   and copy the path returned by that command.

4. Deactivate your environment and start Spyder from your root or base one.

5. Go to

   Tools > Preferences > Python Interpreter > Use the following interpreter

   and paste there the path you got in step 3.

6. Start a new IPython console and run

   from dolfin import *

   It should work now.

This is a standard Unix Makefile, but it's using weird variable names.

The first few lines are all assignments: