More QC opcodes

[divVerent]

• OP_DIV_U (and other _U operations)
• OP_RSHIFT_* and OP_LSHIFT_*

These should all be straightforward and uncontroversial to add, so let's just do it. Reference impl in FTEQW.

[Baker7]

• OP_DIV_U (and other _U operations)

  • OP_RSHIFT_* and OP_LSHIFT_*

These should all be straightforward and uncontroversial to add, so let's just do it. Reference impl in FTEQW.

I noticed you did fte pointer commits and numerous other VM upgrades with and I am excited about those changes.

Are you aware of sample code for fte pointers (and will these changes allow some form of dynamic arrays?).

I would be more than happy to test out the new VM capabilities in the coming weeks, if I can determine exactly how to write the QC to get the engine to do it. I use https://icculus.org/~marco/quakec/fteqcc_manual.txt largely as a reference and the Xonotic QuakeC source, those fteqcc docs talk about pointers but no examples.

[divVerent]

Are you aware of sample code for fte pointers (and will these changes allow some form of dynamic arrays?).

It works with regular FTEQCC and handles fixed size arrays. These changes do NOT provide yet any way for dynamic memory allocation - I did "reserve" some "address space" for that purpose for the future, but that part is not done yet.

Currently you can use a #pragma to enable any opcode you want for your code base - that is how I tested the previously added opcodes. See #215 (comment) for how to enable it.