diff options
| author | Lynne <dev@lynne.ee> | 2021-08-25 21:20:18 +0200 |
|---|---|---|
| committer | Lynne <dev@lynne.ee> | 2021-08-28 15:13:55 +0200 |
| commit | 033105a73901cf9ecfa6d410e96d7f347dc69c71 (patch) | |
| tree | 5b5e9bd5ca7a091a7d6e4ce9f7ec96485f85db5c /libavcodec | |
| parent | 1da524121cf2f796f5ed2e1aecc18ad6dab3771c (diff) | |
h274: remove optimization pragma
This results in warnings on compilers which don't support it,
objections were raised during the review process about it but went unnoticed,
and the speed benefit is highly compiler and version specific, and
also not very critical.
We generally hand-write assembly to optimize loops like that, rather
than use compiler magic, and for 40% best case scenario, it's simply
not worth it.
Plus, tree vectorization is still problematic with GCC and disabled by default
for a good reason, so enabling it locally is sketchy.
Diffstat (limited to 'libavcodec')
| -rw-r--r-- | libavcodec/h274.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/libavcodec/h274.c b/libavcodec/h274.c index 0efc00ca1d..5e2cf150ea 100644 --- a/libavcodec/h274.c +++ b/libavcodec/h274.c @@ -30,10 +30,6 @@ #include "h274.h" -// The code in this file has a lot of loops that vectorize very well, this is -// about a 40% speedup for no obvious downside. -#pragma GCC optimize("tree-vectorize") - static const int8_t Gaussian_LUT[2048+256]; static const uint32_t Seed_LUT[256]; static const int8_t R64T[64][64]; |