aboutsummaryrefslogtreecommitdiffstats
path: root/libavutil/tests
diff options
context:
space:
mode:
authorsoftworkz <softworkz@hotmail.com>2022-05-28 15:07:00 +0000
committerMarton Balint <cus@passwd.hu>2022-06-08 22:24:31 +0200
commit22ab2a375dcac2c9247f099cfef71ca9236a72b1 (patch)
treec60f7dec4be3479e3601cbd79bf311e911f31260 /libavutil/tests
parentb6c856b6e4b5d0b24226a6de173286c380054d88 (diff)
downloadffmpeg-22ab2a375dcac2c9247f099cfef71ca9236a72b1.tar.gz
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 <softworkz@hotmail.com> Signed-off-by: Marton Balint <cus@passwd.hu>
Diffstat (limited to 'libavutil/tests')
-rw-r--r--libavutil/tests/md5.c4
1 files 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;