i is used to denote the usage of 1024 as a base. These are read as kibibyte, mebibyte, an so forth. i.e.:

1024byte = 1KiB
1024KiB  = 1MiB
1024MiB  = 1GiB
etc...

Uppercase B is used for bytes, whilst lowercase b is for bits.

Checked and approved.

Nice!

>> operator has lower precedence than addition, but it's easier on an eye when the left side is inside the braces.

But useless =~)

Nice, readable code!

Mine only got worse after having to use rdx...

done

At this point I can just port normal tests here (except for big ones)

There might be! Mayhap if someone will make one (or when I'll come up with a solution that fast (I might have some ideas)).

[>] moved

Thank you for the review! Now things should be more proper.

I still left some adscititious functions like print and convert available in case someone will want to use them.

Finally made a NASM version... which barely holds together.

I might have to take a look at that.

That was not the only typo, but thanks. I'm trying to fix things now.

1. I completely removed time checks
2. Will add some sample tests (It's a bit hard since there can be infinitely many right answers)
3. It's the other way around. The swap is to show that the order of parameters doesn't matter (basically no matter which one is first, it will alays sort them out)