The C code is doing the "orchestration", the heavy lifting is done by the library routines and as you can see, they looks well optimized because it runs really smooth ! :) Now if you like asm better, you can also do it (with GNU-as)
as you can see, the game runs at 50fps, you can't make it faster than that ;) The recent GCC compiler with the compilation flags I use makes a pretty decent code generation, way better than the old Pure C compiler for example, and as already said, my library contains 50% of assembler code for all the critic parts.
Bravo!
Super boulot c'est de la bombe cette bibliothèque !
merci :)
4:00 BlitterCopyBitmap4 what about performance in "C" vs assembler ?
My library contains 50% of assembly code, the GIF loading, all the blitter functions, the VBL hook, the sound mixer are all in optimized assembly
There is a lot od easier write code in "C" instead of assembler, but... what about the performance ?
The C code is doing the "orchestration", the heavy lifting is done by the library routines and as you can see, they looks well optimized because it runs really smooth ! :) Now if you like asm better, you can also do it (with GNU-as)
as you can see, the game runs at 50fps, you can't make it faster than that ;) The recent GCC compiler with the compilation flags I use makes a pretty decent code generation, way better than the old Pure C compiler for example, and as already said, my library contains 50% of assembler code for all the critic parts.