Here is a particularly bad example of autovectorisation across many
compilers:
https://gcc.godbolt.org/z/rjEqzf1hh
Kieran
Admittedly, in some cases, enabling vectorization is not the optimal
solution.
But the question is the limitation is only added on gcc side.For LLVM
clang, there are no same restrict.
And force add the limitation in configure side will change the user's
original purpose, if user want to
enable the vectorization when using gcc, it will have vectorization
turned off without knowing it.
After a long and careful inspection, user may finally find that the
configure configuration has forced
this feature to be turned off, and they still need to remove this
restriction manually.
BR,
Jiawei
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
