Frama-C-discuss mailing list archives
This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Frama-c-discuss] checking Monocypher
- Subject: [Frama-c-discuss] checking Monocypher
- From: julien.signoles at cea.fr (Julien Signoles)
- Date: Thu, 30 Apr 2020 12:45:02 +0200
- In-reply-to: <CA+yPOVibHp68er_=rvDD+8-Ap1ydpJjVEwLAB_q4oKRuzj1B1Q@mail.gmail.com>
- References: <e63c109dad96e6491a13600f4eddf717@disroot.org> <CA+yPOVibHp68er_=rvDD+8-Ap1ydpJjVEwLAB_q4oKRuzj1B1Q@mail.gmail.com>
Hello, > With the current master, e-acsl-gcc.sh --rte=all monocypher.c > generates an instrumented file (using monocypher 3.1.0), albeit with a > lot of warning stemming from the fact that E-ACSL does not support > bitwise operations in ACSL annotations. It means that these annotations are not checked at runtime. BTW the E-ACSL support for ACSL bitwise operations is planned to be available in the Git repo in a few weeks :-). Best regards, Julien
- References:
- [Frama-c-discuss] checking Monocypher
- From: tankf33der at disroot.org (Mike)
- [Frama-c-discuss] checking Monocypher
- From: virgile.prevosto at m4x.org (Virgile Prevosto)
- [Frama-c-discuss] checking Monocypher
- Prev by Date: [Frama-c-discuss] checking Monocypher
- Next by Date: [Frama-c-discuss] checking Monocypher
- Previous by thread: [Frama-c-discuss] checking Monocypher
- Next by thread: [Frama-c-discuss] checking Monocypher
- Index(es):