> Very few instructions even allowed interaction between the top and bottom 128 bits That would be plain AVX, AVX2 has shuffles across the 128-bit boundary. To me that seems like the main hurdle for emulation with…
In the branchy function, id is only compared if distance is equal, and since distance is a random float, this almost never happens and the corresponding branch is nearly perfectly predicted. The branchless function…
You're right that it's not exactly n^2. For the i-th element we perform (n - i - 1) comparisons (indexing from 0). This adds up to a total of (n - 1) * n / 2 comparisons. (see…
Is this still the case with recent audio hardware? I was under the impression that a typical instrument's output levels are far too low to cause any damage and that all inputs would be surge protected.
Apps aren't being written _on purpose_ to rely on the allocator doing nothing with freed memory because that's not in its interface, and this change doesn't actually do anything to stop apps from reading freed memory.…
Haven't read the entire post yet, but must say that this was the page that finally made me look into how a webpage works so I could hide the gifs to read the actual content in peace. Why would anyone, much less a…
> Very few instructions even allowed interaction between the top and bottom 128 bits That would be plain AVX, AVX2 has shuffles across the 128-bit boundary. To me that seems like the main hurdle for emulation with…
In the branchy function, id is only compared if distance is equal, and since distance is a random float, this almost never happens and the corresponding branch is nearly perfectly predicted. The branchless function…
You're right that it's not exactly n^2. For the i-th element we perform (n - i - 1) comparisons (indexing from 0). This adds up to a total of (n - 1) * n / 2 comparisons. (see…
Is this still the case with recent audio hardware? I was under the impression that a typical instrument's output levels are far too low to cause any damage and that all inputs would be surge protected.
Apps aren't being written _on purpose_ to rely on the allocator doing nothing with freed memory because that's not in its interface, and this change doesn't actually do anything to stop apps from reading freed memory.…
Haven't read the entire post yet, but must say that this was the page that finally made me look into how a webpage works so I could hide the gifs to read the actual content in peace. Why would anyone, much less a…