Remix.run Logo
▲ bullen 3 hours ago

This is the code I use since 20 years back:

http://move.rupy.se/file/base64.txt

If this part becomes the bottleneck; so I need to write a GPU accelerated version I'll eat my own hat.

▲layer8 2 hours ago | parent | next [-]

Your decoder implementation accepts all sorts of non-Base64 strings and decodes them to whatever. Among other things, it also accepts MIME Base64 (with line breaks and whitespace) and base64url strings, but decodes them to the wrong values. This is a classic example of insufficient input validation that can lead to parser mismatch vulnerabilities or worse.

▲CAP_NET_ADMIN 3 hours ago | parent | prev [-]

Vectorized base64 can reach speeds in the proximity of memory copy.

I've easily reached a point where it was worth it to go AVX route in my "for funsies" game that I'm making.

▲ 2 hours ago | parent | next [-]
[deleted]
▲CAP_NET_ADMIN 3 hours ago | parent | prev [-]

Just checked, the scalar version reaches around 1-2GB/s when decoding, optimized it gets to 4GB/s, AVX-512 VBMI version reaches 40-55GB/s.

▲bullen 3 hours ago | parent [-]

Interesting, what game are you making?

▲CAP_NET_ADMIN 3 hours ago | parent [-]

Large scale tower/base defense with time rewind mechanics and user-generated structure templates.

▲bullen an hour ago | parent [-]

So where do you need 40GB/s of base64?