From f8155f0b945c5cfb3600d7c146a5d86870ed09d2 Mon Sep 17 00:00:00 2001
From: jvoisin
Date: Tue, 8 Oct 2024 03:51:44 +0200
Subject: Run various C versions in the CI

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'README.md')

diff --git a/README.md b/README.md
index 86e73fc..e187776 100644
--- a/README.md
+++ b/README.md
@@ -21,8 +21,9 @@ on Clang. It was initially intended to be used on
 - Support for out-of-bounds read interfaces, such as send(), write(), fwrite() etc.
 - No ABI is enforced. All of the fortify check functions are inlined
   into the resulting binary.
-- It has a [comprehensive suite of tests](https://github.com/jvoisin/fortify-headers/tree/master/tests),
-  running both on Clang and on GCC for every commit, with
+- It has a [comprehensive suite of
+  tests](https://github.com/jvoisin/fortify-headers/tree/master/tests), running
+  both on Clang and on GCC for every commit, on C89, C99, C11 and C17, with
   [significant coverage](https://jvoisin.github.io/fortify-headers/)
 - Defining `FORTIFY_USE_NATIVE_CHK` will make use of compiler-provided builtin `_chk`
   functions, which might be a bit better in term of diagnostics,
-- 
cgit v1.3