From 22ab2a375dcac2c9247f099cfef71ca9236a72b1 Mon Sep 17 00:00:00 2001 From: softworkz Date: Sat, 28 May 2022 15:07:00 +0000 Subject: [PATCH] libavutil/tests/md5: Remove 'volatile workaround' to avoid warnings Those are always showing up on Patchwork when FATE tests are failing, covering some possibly more useful information. The volatile keyword was used as a workaround for an eight year old clang version. Signed-off-by: softworkz Signed-off-by: Marton Balint --- libavutil/tests/md5.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libavutil/tests/md5.c b/libavutil/tests/md5.c index 42e4538e0a..0ac8f2834e 100644 --- a/libavutil/tests/md5.c +++ b/libavutil/tests/md5.c @@ -33,8 +33,8 @@ int main(void) { uint8_t md5val[16]; int i; - volatile uint8_t in[1000]; // volatile to workaround http://llvm.org/bugs/show_bug.cgi?id=20849 - // FIXME remove volatile once it has been fixed and all fate clients are updated + + uint8_t in[1000]; for (i = 0; i < 1000; i++) in[i] = i * i;