Both GCC and Clang can switch off the braindead type-based aliasing rules through the "-fno-strict-aliasing" compiler option so that everything can alias everything.

On the other hand, C offers the "restrict" qualifier for pointers where you promise that nothing will alias this memory area, not even same type pointers.

What happens if you use "restrict", but compile with "-fno-strict-aliasing"? Will the "restrict" be obeyed or disregarded?

Answer in the comments.

Muahahaha!
Stupid canvas! I killed you!
No more anti-aliasing for you! Now it's time for pixel perfect drawings and a finally functioning floodfill algorithm!
I only had to make my own full custom drawing routine. It is not that I had other things to do, right?!

Seriously: Who the heck decided to implement anti-aliasing for a canvas that cannot be deactivated? Who!?

Oh, I hate frontend so much. That's not my world...