They tested the same strings on that implementation
The strings were the same, but not the implementation. They were testing the decoding of the strings, but the C function they were looking at was the one for encoding them. The decoding function was correct but what it read didn't match the encoding one.
though judging by the recent comments someone’s found something.
Yeah, that's me :)
while a similar C implementation does not need this fix
No, that implementation also needs the fix. It's just that it was never properly tested, so they thought it was working correctly.
It's also extremely unlikely that you'd be running a bat script with untrusted arguments on Windows.
It happens in yt-dl, which is where this was first reported https://github.com/yt-dlp/yt-dlp/security/advisories/GHSA-hjq6-52gw-2g7p
Loop unrolling is not really the speedup, autovectorization is. Loop unrolling does often help with autovectorization, but is not enough, especially with floating point numbers. In fact the accumulation operation you're doing needs to be associative, and floating point numbers addition is not associative (i.e. (x + y) + z is not always equal to (x + (y + z)). Hence autovectorizing the code would change the semantics and the compiler is not allowed to do that.
However, how are they sabotaging it working on Linux.
For example they discontinued support for Rocket League on Linux (and Mac) after buying Psyonix.
Even if the compiler was available to the public most software doesn't use it, so the benchmark is still not representative of real world performance.
People can only remember a limited number of passwords without resorting to systems or patterns.
People also don't have a backup device though.
I wonder why this is not a problem for pcs though
As for the browser, I’d be glad if Chrome died. We need more browsers. Chrome dying would force all of the derivatives to do something else. Vivaldi, edge, brave, etc would all need to either switch to Firefox or a project for a new browser would begin
Firefox is currently kept alive by Google, which pays $500M/year to Mozilla in order to have Google Search as the default in Firefox and to not let Google Chrome become a monopoly on paper too. Break Google and it would probably die.
Creating "more browsers" (browser engines I would add, we already have enough browsers) is not an easy task. The specification that needs to be implemented is massive, and doing so efficiently is even more complex. It would be a waste of resources to have many browser engines, not to mention the confusion in the webdev community when you suddently have to work around many more bugs in the implementations.
Yeah, and none of them let you keep your existing @gmail.com address. Which means you'll have to update it everywhere. That's the massive problem.
Sounds like your Firefox is not using hardware acceleration for displaying videos. It does support it, but whether it will be enabled on Linux depends on a bunch of factors (distro/packages installed, cpu/gpu vendor/drivers, some weird settings etc etc)
Isn't there already Box64/Box32? Not to mention most Linux software is already compiled for ARM thanks to being open source.