> A compiler that conforms to the ABI generates code which clears the flag, if necessary. I'm sorry, I do not follow. The conforming compiler expects that the functions are called with the clear flag. The non-conforming…
> The flag can have arbitrary value in on entry to memcpy in an ordinary situation not involving threads or signals. It can not have arbitrary value on entry. x86-64 ABI mandates that the flag is cleared before any…
The x86-64 ABI does not require frame pointer setup: https://godbolt.org/g/10URYW
Do you have benchmarks, supporting "~break-even vs. 128 bit AVX on Ivy Bridge from 128 bytes up to 2KB" as I have not found it to be the case at least on Haskell (my benchmarking code is @…
> A compiler that conforms to the ABI generates code which clears the flag, if necessary. I'm sorry, I do not follow. The conforming compiler expects that the functions are called with the clear flag. The non-conforming…
> The flag can have arbitrary value in on entry to memcpy in an ordinary situation not involving threads or signals. It can not have arbitrary value on entry. x86-64 ABI mandates that the flag is cleared before any…
The x86-64 ABI does not require frame pointer setup: https://godbolt.org/g/10URYW
Do you have benchmarks, supporting "~break-even vs. 128 bit AVX on Ivy Bridge from 128 bytes up to 2KB" as I have not found it to be the case at least on Haskell (my benchmarking code is @…