Wouter van Oortmerssen

I have personally never tested it with RPi (don't have one), and not sure anyone else has.. it must simply work well with "generic" CMake. I left out the arm...

That's not the official site, I got the files from https://bellard.org/tcc/ I did not make any changes to the files in `dev/externel/libtcc`

Which version of Lobster is this? you should be on latest master. For me, `error: arguments match no overloads of float` is not happening on any platforms, so either that...

Lobster should still build for 32-bit platforms, as we have CI to build for wasm32 for example. But yes, everything else is 64-bit. 64-bit RPi is apparently happening, cool :)...

Can you point me to how that would work? How would you work on this machine? I can imagine SSHing into it, but that would not be sufficient for testing...

Ok, that sounds like a minimal enough investment that I could get a RPi 4 to try this out. I have a mac laptop with usb-c which sounds like it...

That's an intentional limitation that should probably be documented for the moment. It was there to not explode the number of VM vector operations. Though I guess it just needs...

Why? `4 / xy { 2, 1 }` could result in `xy { 2, 4 }`, no different from `-`. The other way around is just more natural to read,...

@bartwe those are exactly the kind of uses that this would not address, i.e. more fixed size game/graphics oriented types. But you're right, so far we have avoided having those...

@stefandd as for a code explosion, we currently already have several hundred VM ops dealing just with these fixed int/float vectors. It's int vs float, vector vs scalar, lvalue vs...